Triple
T31428908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkmen rail network |
E801738
|
entity |
| Predicate | keyCorridor |
P132404
|
FINISHED |
| Object | North–South Transport Corridor |
—
|
NE NERFINISHED |
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: North–South Transport Corridor | Statement: [Turkmen rail network, keyCorridor, North–South Transport Corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyCorridor Context triple: [Turkmen rail network, keyCorridor, North–South Transport Corridor]
-
A.
keySector
Indicates that an entity operates in, belongs to, or is primarily associated with a particularly important or strategic sector within a broader domain or economy.
-
B.
keyTransitArea
Indicates that a location functions as a primary passage or hub through which movement or transport between other areas is concentrated or facilitated.
-
C.
linkedByCorridor
Indicates that two locations are directly connected to each other by a corridor.
-
D.
keyFortress
Indicates that one entity functions as a key or means of access, control, or unlocking for a particular fortress or strongly secured place represented by the other entity.
-
E.
inCorridor
chosen
Indicates that one entity is located within or inside a corridor relative to another spatial context or reference.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:55 p.m.