Triple
T5520545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhangjiakou |
E144793
|
entity |
| Predicate | strategicCorridor |
P3034
|
FINISHED |
| Object | route from Beijing to Mongolia |
—
|
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: route from Beijing to Mongolia | Statement: [Zhangjiakou, strategicCorridor, route from Beijing to Mongolia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicCorridor Context triple: [Zhangjiakou, strategicCorridor, route from Beijing to Mongolia]
-
A.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
B.
isIndustrialCorridor
Indicates that an area or route is designated and used primarily for industrial activities, facilities, or transportation.
-
C.
transportCorridor
chosen
Indicates a route or pathway used to move people, goods, or resources between locations.
-
D.
hasStrategicStrait
Indicates that one entity possesses or controls a strategically important narrow waterway that is relevant to another entity.
-
E.
strategicArea
Indicates that an entity is designated as an area of strategic importance or priority within a broader plan, operation, or context.
- 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_69c008f873a481909b4d9f7e2db3c37d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f7082ac8190a372fa75e8dec6a4 |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.