Triple
T30155431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 长江 |
E766507
|
entity |
| Predicate | 经济作用 |
P12253
|
FINISHED |
| Object | 中国重要内河航运通道 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 中国重要内河航运通道 | Statement: [长江, 经济作用, 中国重要内河航运通道]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 经济作用 Context triple: [长江, 经济作用, 中国重要内河航运通道]
-
A.
economicFunction
chosen
Indicates the role or purpose an entity serves within an economic system, such as how it contributes to production, distribution, or consumption of goods and services.
-
B.
impactOnEconomy
Indicates the effect or influence that one factor, event, or action has on the state or performance of an economy.
-
C.
economicAspect
Indicates that something is related to, characterized by, or has implications for economic factors, conditions, or outcomes.
-
D.
stanceOnEconomy
Indicates a subject's expressed position, opinion, or policy view regarding economic issues or economic policy.
-
E.
hasEconomicImplication
Indicates that one entity’s state, action, or relationship has a direct or indirect impact on the economic conditions, costs, or financial outcomes of another entity or system.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed72fb08190955d6bfd90dd3b8e |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:20 p.m.