Triple
T10381652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Edward Viaduct |
E244654
|
entity |
| Predicate | subwayServiceBegan |
P61760
|
FINISHED |
| Object | 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: 1966 | Statement: [Prince Edward Viaduct, subwayServiceBegan, 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subwayServiceBegan Context triple: [Prince Edward Viaduct, subwayServiceBegan, 1966]
-
A.
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.
-
B.
openedAsSubway
Indicates that a transportation facility or line originally began operation specifically as a subway service.
-
C.
subwaySectionOpened
chosen
Indicates that a specific section of a subway line has officially begun operation or been opened for public use.
-
D.
subwayServices
Indicates that one entity provides or operates subway transportation services for another entity or area.
-
E.
commuterServiceBegan
Indicates that a commuter transportation service was initiated or began operating between specified locations or entities.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9921fa48190a874aa9a9e385b97 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:04 p.m.