Triple
T24132960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Michel station |
E598003
|
entity |
| Predicate | hasAdjacentStationOnBlueLine |
P62965
|
FINISHED |
| Object | D’Iberville station |
—
|
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: D’Iberville station | Statement: [Saint-Michel station, hasAdjacentStationOnBlueLine, D’Iberville station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentStationOnBlueLine Context triple: [Saint-Michel station, hasAdjacentStationOnBlueLine, D’Iberville station]
-
A.
adjacentStationOnBlueLine
chosen
Indicates that one station is directly next to another station along the Blue Line in the transit network.
-
B.
hasAdjacentStationOnYellowLine
Indicates that one station is directly next to another station along the yellow transit line.
-
C.
hasAdjacentStationOnRedLine
Indicates that one station is directly next to another station along the red transit line, with no other stations in between.
-
D.
hasAdjacentStationOnGreenLine
Indicates that one station is directly next to another station along the Green Line.
-
E.
hasAdjacentStationOnPurpleLine
Indicates that one station is directly next to another station along the Purple Line in the transit network.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df79bfd08190970ed1b3f14ebc8b |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:26 p.m.