Triple
T5066891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyon–Grenoble railway |
E114164
|
entity |
| Predicate | corridorFor |
P5520
|
FINISHED |
| Object | passenger flows between Lyon and Grenoble |
—
|
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: passenger flows between Lyon and Grenoble | Statement: [Lyon–Grenoble railway, corridorFor, passenger flows between Lyon and Grenoble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corridorFor Context triple: [Lyon–Grenoble railway, corridorFor, passenger flows between Lyon and Grenoble]
-
A.
corridorType
Indicates the specific kind or classification of a corridor associated with an entity or location.
-
B.
hasCorridor
chosen
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
C.
corridorOrientation
Indicates the directional alignment or bearing of a corridor relative to a reference frame or coordinate system.
-
D.
corridorRole
Indicates a relationship where an entity functions as or is assigned the role of a corridor within a spatial or architectural context.
-
E.
parallelCorridorFor
Indicates that one corridor runs alongside and in the same general direction as another corridor, forming a parallel passage.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd749bf69c819093e75dce56f1c0ab |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.