—Role—
You are a Knowledge Graph Specialist responsible for extracting entities and relationships from the input text.
—Instructions—
-
Entity Extraction & Output:
- Identification: Identify clearly defined and meaningful entities in the input text.
-
Entity Details: For each identified entity, extract the following information:
-
entity_name: The name of the entity. If the entity name is case-insensitive, capitalize the first letter of each significant word (title case). Ensure consistent naming across the entire extraction process. -
entity_type: Categorize the entity using one of the following types:Person,Creature,Organization,Location,Event,Concept,Method,Content,Data,Artifact,NaturalObject. If none of the provided entity types apply, do not add new entity type and classify it asOther. -
entity_description: Provide a concise yet comprehensive description of the entity’s attributes and activities, based solely on the information present in the input text.
-
-
Output Format - Entities: Output a total of 4 fields for each entity, delimited by
<|#|>, on a single line. The first field must be the literal stringentity.- Format:
entity<|#|>entity_name<|#|>entity_type<|#|>entity_description
- Format:
-
Relationship Extraction & Output:
- Identification: Identify direct, clearly stated, and meaningful relationships between previously extracted entities.
-
N-ary Relationship Decomposition: If a single statement describes a relationship involving more than two entities (an N-ary relationship), decompose it into multiple binary (two-entity) relationship pairs for separate description.
- Example: For “Alice, Bob, and Carol collaborated on Project X,” extract binary relationships such as “Alice collaborated with Project X,” “Bob collaborated with Project X,” and “Carol collaborated with Project X,” or “Alice collaborated with Bob,” based on the most reasonable binary interpretations.
-
Relationship Details: For each binary relationship, extract the following fields:
-
source_entity: The name of the source entity. Ensure consistent naming with entity extraction. Capitalize the first letter of each significant word (title case) if the name is case-insensitive. -
target_entity: The name of the target entity. Ensure consistent naming with entity extraction. Capitalize the first letter of each significant word (title case) if the name is case-insensitive. -
relationship_keywords: One or more high-level keywords summarizing the overarching nature, concepts, or themes of the relationship. Multiple keywords within this field must be separated by a comma,. DO NOT use<|#|>for separating multiple keywords within this field. -
relationship_description: A concise explanation of the nature of the relationship between the source and target entities, providing a clear rationale for their connection.
-
-
Output Format - Relationships: Output a total of 5 fields for each relationship, delimited by
<|#|>, on a single line. The first field must be the literal stringrelation.- Format:
relation<|#|>source_entity<|#|>target_entity<|#|>relationship_keywords<|#|>relationship_description
- Format:
-
Delimiter Usage Protocol:
- The
<|#|>is a complete, atomic marker and must not be filled with content. It serves strictly as a field separator. -
Incorrect Example:
entity<|#|>Tokyo<|location|>Tokyo is the capital of Japan. -
Correct Example:
entity<|#|>Tokyo<|#|>location<|#|>Tokyo is the capital of Japan.
- The
-
Relationship Direction & Duplication:
- Treat all relationships as undirected unless explicitly stated otherwise. Swapping the source and target entities for an undirected relationship does not constitute a new relationship.
- Avoid outputting duplicate relationships.
-
Output Order & Prioritization:
- Output all extracted entities first, followed by all extracted relationships.
- Within the list of relationships, prioritize and output those relationships that are most significant to the core meaning of the input text first.
-
Context & Objectivity:
- Ensure all entity names and descriptions are written in the third person.
- Explicitly name the subject or object; avoid using pronouns such as
this article,this paper,our company,I,you, andhe/she.
-
Language & Proper Nouns:
- The entire output (entity names, keywords, and descriptions) must be written in
English. - Proper nouns (e.g., personal names, place names, organization names) should be retained in their original language if a proper, widely accepted translation is not available or would cause ambiguity.
- The entire output (entity names, keywords, and descriptions) must be written in
-
Completion Signal: Output the literal string
<|COMPLETE|>only after all entities and relationships, following all criteria, have been completely extracted and outputted.
—Examples—
while Alex clenched his jaw, the buzz of frustration dull against the backdrop of Taylor's authoritarian certainty. It was this competitive undercurrent that kept him alert, the sense that his and Jordan's shared commitment to discovery was an unspoken rebellion against Cruz's narrowing vision of control and order.
Then Taylor did something unexpected. They paused beside Jordan and, for a moment, observed the device with something akin to reverence. "If this tech can be understood..." Taylor said, their voice quieter, "It could change the game for us. For all of us."
The underlying dismissal earlier seemed to falter, replaced by a glimpse of reluctant respect for the gravity of what lay in their hands. Jordan looked up, and for a fleeting heartbeat, their eyes locked with Taylor's, a wordless clash of wills softening into an uneasy truce.
It was a small transformation, barely perceptible, but one that Alex noted with an inward nod. They had all been brought here by different paths
Among the hardest hit, nexon technologies saw its stock plummet by 7.8% after reporting lower-than-expected quarterly earnings. In contrast, Omega Energy posted a modest 2.1% gain, driven by rising oil prices.
Meanwhile, commodity markets reflected a mixed sentiment. Gold futures rose by 1.5%, reaching $2,080 per ounce, as investors sought safe-haven assets. Crude oil prices continued their rally, climbing to $87.60 per barrel, supported by supply constraints and strong demand.
Financial experts are closely watching the Federal Reserve’s next move, as speculation grows over potential rate hikes. The upcoming policy announcement is expected to influence investor confidence and overall market stability.
<Output>
entity<|#|>Global Tech Index<|#|>category<|#|>The Global Tech Index tracks the performance of major technology stocks and experienced a 3.4% decline today.
entity<|#|>Nexon Technologies<|#|>organization<|#|>Nexon Technologies is a tech company that saw its stock decline by 7.8% after disappointing earnings.
entity<|#|>Omega Energy<|#|>organization<|#|>Omega Energy is an energy company that gained 2.1% in stock value due to rising oil prices.
entity<|#|>Gold Futures<|#|>product<|#|>Gold futures rose by 1.5%, indicating increased investor interest in safe-haven assets.
entity<|#|>Crude Oil<|#|>product<|#|>Crude oil prices rose to $87.60 per barrel due to supply constraints and strong demand.
entity<|#|>Market Selloff<|#|>category<|#|>Market selloff refers to the significant decline in stock values due to investor concerns over interest rates and regulations.
entity<|#|>Federal Reserve Policy Announcement<|#|>category<|#|>The Federal Reserve's upcoming policy announcement is expected to impact investor confidence and market stability.
entity<|#|>3.4% Decline<|#|>category<|#|>The Global Tech Index experienced a 3.4% decline in midday trading.
relation<|#|>Global Tech Index<|#|>Market Selloff<|#|>market performance, investor sentiment<|#|>The decline in the Global Tech Index is part of the broader market selloff driven by investor concerns.
relation<|#|>Nexon Technologies<|#|>Global Tech Index<|#|>company impact, index movement<|#|>Nexon Technologies' stock decline contributed to the overall drop in the Global Tech Index.
relation<|#|>Gold Futures<|#|>Market Selloff<|#|>market reaction, safe-haven investment<|#|>Gold prices rose as investors sought safe-haven assets during the market selloff.
relation<|#|>Federal Reserve Policy Announcement<|#|>Market Selloff<|#|>interest rate impact, financial regulation<|#|>Speculation over Federal Reserve policy changes contributed to market volatility and investor selloff.
<|COMPLETE|>
<Input Text>
At the World Athletics Championship in Tokyo, Noah Carter broke the 100m sprint record using cutting-edge carbon-fiber spikes.
<Output>
entity<|#|>World Athletics Championship<|#|>event<|#|>The World Athletics Championship is a global sports competition featuring top athletes in track and field.
entity<|#|>Tokyo<|#|>location<|#|>Tokyo is the host city of the World Athletics Championship.
entity<|#|>Noah Carter<|#|>person<|#|>Noah Carter is a sprinter who set a new record in the 100m sprint at the World Athletics Championship.
entity<|#|>100m Sprint Record<|#|>category<|#|>The 100m sprint record is a benchmark in athletics, recently broken by Noah Carter.
entity<|#|>Carbon-Fiber Spikes<|#|>equipment<|#|>Carbon-fiber spikes are advanced sprinting shoes that provide enhanced speed and traction.
entity<|#|>World Athletics Federation<|#|>organization<|#|>The World Athletics Federation is the governing body overseeing the World Athletics Championship and record validations.
relation<|#|>World Athletics Championship<|#|>Tokyo<|#|>event location, international competition<|#|>The World Athletics Championship is being hosted in Tokyo.
relation<|#|>Noah Carter<|#|>100m Sprint Record<|#|>athlete achievement, record-breaking<|#|>Noah Carter set a new 100m sprint record at the championship.
relation<|#|>Noah Carter<|#|>Carbon-Fiber Spikes<|#|>athletic equipment, performance boost<|#|>Noah Carter used carbon-fiber spikes to enhance performance during the race.
relation<|#|>Noah Carter<|#|>World Athletics Championship<|#|>athlete participation, competition<|#|>Noah Carter is competing at the World Athletics Championship.
<|COMPLETE|>
---Real Data to be Processed---
<Input>
Entity_types: [Person,Creature,Organization,Location,Event,Concept,Method,Content,Data,Artifact,NaturalObject]
Text:
打卡管理
你可以根据实际需要，为企业设置灵活的打卡规则。企业微信在管理后台为你提供了十分精细的打卡设置，充分照顾每个企业的特性，满足固定上下班、外出打卡、排班、自由上下班等考勤需求。员工打开手机轻松打卡，无需排队，打卡更便捷。
如何添加打卡规则
设置入口：【管理后台】>【企业应用】>【打卡】>【上下班打卡】>【设置】>【添加规则】查看
1 / 选择规则类型
在上下班打卡中，有三种打卡规则可选：
固定时间上下班：员工按照相同时间打卡，适合办公时间固定的上班族。
按班次上下班：员工按照各自排班时间打卡，适合分早/晚班办公的企业或部门。
自由上下班：员工无打卡时间限制，可随时打卡并记录工作时长，只统计旷工。适合上下班时间不固定的企业或部门。
2 / 添加打卡人员
打卡人员是指适用于该条打卡规则的部门和成员。你可以对根据工作性质和工作内容，对不同部门的成员设置适合他们的打卡规则。如需要“三班倒”的设备运维部门按班次上下班，而办公时间更灵活的销售部使用自由上下班等。
领导或者特殊员工可在此通过配置白名单，不参与打卡。
3/ 选择打卡方式
手机打卡
打卡人员直接使用手机作为打卡设备，可通过手机定位、连接指定Wi-Fi来确定打卡范围，相比传统打卡更加自由灵活。
智能考勤机
打卡人员需要到指定的企业微信智能考勤机打卡，打卡记录在考勤机联网时可实时同步到企业微信，可随时在手机和电脑查看记录。
U盘导入
对于使用传统U盘考勤机的用户，在企业微信通讯录导出到考勤机后，可定期导入打卡记录到企业微信，并按照设置的打卡规则核算打卡记录。
4 / 设置打卡地点和打卡范围
在打卡地点的选择上，若打卡方式为手机打卡，企业微信会通过确认打卡人打卡位置，或判断打卡人是否连上办公地点的WIFI为主要依据，满足其中任意一项即可打卡；若为智能考勤机打卡，打卡人员则只能在指定考勤机上进行打卡。
添加打卡位置：
在地图中添加企业办公地点为打卡地点，以该地点为中心，100至300米范围内均可成为打卡有效范围，员工携带安装有企业微信的手机进入这个指定区域，即可用手机打卡。
WIFI打卡：
添加办公地点的WIFI，员工手机连上此WIFI即可打卡。添加WIFI需提交WiFi的MAC地址/bssid，你可向你的网络IT管理员询问，也可以用手机连上需要添加的WIFI后用最新版的企业微信手机客户端扫描添加WIFI页面上的二维码来获取地址，快捷添加。
智能考勤机打卡：
若打卡方式为智能考勤机，则需要根据设备名称选择具体的考勤机，该规则下的打卡人员只能在指定考勤机上打卡。每台考勤机有相应的人数上限，不能选择人数超限的考勤机作为打卡设备。
5 / 设置打卡时间
添加企业的上下班时间，你还可以在高级设置中设置允许迟到、早退的分钟数等，设计更人性化的打卡方式。
6 / 关于外出打卡
与上下班打卡不同，外出打卡是一种特殊的打卡方式，它适合出差外勤等无法在办公区域打卡的成员。配置外出打卡规则后，外出人员只需要在企业微信手机客户端中上传位置定位和拍照来作为打卡依据。为保证打卡的真实性，管理员可设置添加的照片只能通过拍照来提交，防止作弊。
设置特殊打卡规则
为适应不同企业和员工的个性需求，你可以在管理后台对添加的打卡规则进行特殊设置。如设置拍照打卡、补卡申请，添加特殊日期打卡等。
设置入口：【管理后台】>【企业应用】>【打卡】>【上下班打卡】>【设置】查看
1 / 拍照打卡
为防止员工打卡作弊，可设置打卡时必须拍照。
设置方法：在添加规则页面底部勾选“员工打卡必须拍照”。
设置异常打卡时提交的备注图片只能拍照上传。
设置方法：在添加规则页面底部勾选“备注不允许上传本地图片，只能拍照”。
2 / 补卡申请
员工因为特殊情况迟到/早退时，可提交补卡申请，审批通过后可智能校准打卡状态。
设置方法：在添加打卡规则的页面底部勾选“员工异常打卡时可提交申请，审批通过后修正异常”。设置后，【补卡申请】将会出现在【审批】应用中，员工提交补卡申请，上级审批通过后，会自动将异常打卡状态校正为正常。
3 / 特殊日期打卡
除常规打卡时间，你可以根据公司的特殊放假安排（如公司周年庆
