Triple
T30463557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istanbul–Ankara industrial corridor |
E775073
|
entity |
| Predicate | containsTransportAxis |
P87177
|
FINISHED |
| Object | D100 highway |
—
|
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: D100 highway | Statement: [Istanbul–Ankara industrial corridor, containsTransportAxis, D100 highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsTransportAxis Context triple: [Istanbul–Ankara industrial corridor, containsTransportAxis, D100 highway]
-
A.
isTransportationAxisOf
Indicates that one entity serves as a primary route or corridor used to transport or move another entity from place to place.
-
B.
hasTransportAcross
Indicates that one entity provides or enables transportation across another entity, such as a barrier, region, or medium.
-
C.
isTransport
Indicates that one entity serves as a means or method for conveying or carrying another entity from one place to another.
-
D.
hasTransportationElement
chosen
Indicates that one entity includes, involves, or is associated with a specific transportation-related component or feature.
-
E.
transportAxis
Indicates a directional path or axis along which something is transported or moved from one location to another.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: April 29, 2026, 8:10 p.m.