Triple
T19442049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto public transit network |
E486372
|
entity |
| Predicate | subwayOpeningDate |
P20538
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [Toronto public transit network, subwayOpeningDate, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subwayOpeningDate Context triple: [Toronto public transit network, subwayOpeningDate, 1954]
-
A.
firstSubwayOpeningDate
chosen
Indicates the calendar date on which a subway system or line first began operating.
-
B.
subwaySectionOpened
Indicates that a specific section of a subway line has officially begun operation or been opened for public use.
-
C.
firstSubwayOpeningSegment
Indicates that the subject is the initial segment or section of a subway line that was opened first in its operation or construction sequence.
-
D.
subwayOperation
Indicates the operation or running of a subway system, relating transit services to the times, routes, or conditions under which subway trains are in service.
-
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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63365343081908683c29f6c4c194b |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.