Triple
T30155448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 长江 |
E766507
|
entity |
| Predicate | 相关国家战略 |
P115670
|
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.
hasStrategicImportanceType
Indicates that something is classified according to a specific category or type of strategic importance.
-
B.
strategicRelation
Indicates a relationship where entities are connected through plans, goals, or coordinated actions intended to achieve long-term or high-level objectives.
-
C.
coordinatesNationalPoliciesFor
Indicates that one entity organizes and harmonizes national-level policies or strategies across multiple actors or domains.
-
D.
strategicArea
Indicates that an entity is designated as an area of strategic importance or priority within a broader plan, operation, or context.
-
E.
hasStrategicContext
chosen
Indicates that something is associated with or situated within a broader strategic framework, plan, or set of objectives.
- 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.