Triple
T38400836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E2A |
E900891
|
entity |
| Predicate | hasCorridorFunction |
P80212
|
FINISHED |
| Object | long-distance traffic |
—
|
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: long-distance traffic | Statement: [E2A, hasCorridorFunction, long-distance traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorridorFunction Context triple: [E2A, hasCorridorFunction, long-distance traffic]
-
A.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
B.
corridorFunction
chosen
Indicates that one entity serves as a corridor or passageway functionally connecting or providing access between other spaces or areas.
-
C.
hasCorridorName
Indicates that an entity is associated with or identified by the name of a specific corridor.
-
D.
hasParallelCorridorRole
Indicates that one entity serves in a corridor-related role that is parallel or equivalent to the corridor role of another entity.
-
E.
hasServiceOnCorridor
Indicates that a service operates along, or is provided on, a specific corridor or route.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.