Triple
T9408999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Light Train |
E226658
|
entity |
| Predicate | mayShareCorridorWith |
P35459
|
FINISHED |
| Object | road traffic on semi-exclusive alignments |
—
|
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: road traffic on semi-exclusive alignments | Statement: [Light Train, mayShareCorridorWith, road traffic on semi-exclusive alignments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayShareCorridorWith Context triple: [Light Train, mayShareCorridorWith, road traffic on semi-exclusive alignments]
-
A.
sharesCorridorWith
chosen
Indicates that two entities are located along or connected by the same corridor or passageway.
-
B.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
C.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
D.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
-
E.
mayCoordinate
Indicates that one entity is permitted or has the option to coordinate or work jointly with another entity.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd52547f0c81908ed4f53b9f05ebaa |
completed | April 1, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.