Triple
T9104489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloor Viaduct |
E218442
|
entity |
| Predicate | subwayLineOpenedOnBridge |
P10389
|
FINISHED |
| Object | February 26, 1966 |
—
|
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: February 26, 1966 | Statement: [Bloor Viaduct, subwayLineOpenedOnBridge, February 26, 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subwayLineOpenedOnBridge Context triple: [Bloor Viaduct, subwayLineOpenedOnBridge, February 26, 1966]
-
A.
subwaySectionOpened
Indicates that a specific section of a subway line has officially begun operation or been opened for public use.
-
B.
metroLineInaugurated
chosen
Indicates that a metro line was officially opened and began operation on a specific date or during a specific event.
-
C.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
D.
firstSubwayOpeningDate
Indicates the calendar date on which a subway system or line first began operating.
-
E.
openedAsSubway
Indicates that a transportation facility or line originally began operation specifically as a subway service.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca56f1f10819091abadf7cd06c3a6 |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.