Triple
T27474319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xi'an |
E693411
|
entity |
| Predicate | roleInSilkRoad |
P137851
|
FINISHED |
| Object | eastern terminus |
—
|
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: eastern terminus | Statement: [Xi'an, roleInSilkRoad, eastern terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSilkRoad Context triple: [Xi'an, roleInSilkRoad, eastern terminus]
-
A.
roleInBeltAndRoad
Indicates the specific function, involvement, or capacity an entity has within the context of the Belt and Road Initiative.
-
B.
roleInTibet
Indicates that an entity holds or has held a specific role, position, or function within the context of Tibet.
-
C.
roleInArabia
Indicates that an entity holds or held a specific role, position, or function within the context of Arabia.
-
D.
roleInNepal
Indicates that an entity holds or has held a specific role, position, or function within the context of Nepal.
-
E.
travelRouteRole
chosen
Indicates the specific functional role an entity plays within a travel route, such as origin, destination, or intermediate stop.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 27, 2026, 12:56 p.m.