Triple
T23220104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allen Expressway |
E580862
|
entity |
| Predicate | abruptTerminationAt |
P22869
|
FINISHED |
| Object | Eglinton Avenue West |
—
|
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: Eglinton Avenue West | Statement: [Allen Expressway, abruptTerminationAt, Eglinton Avenue West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abruptTerminationAt Context triple: [Allen Expressway, abruptTerminationAt, Eglinton Avenue West]
-
A.
terminationEndedIn
Indicates that a termination event concluded with a specific outcome or result.
-
B.
wasTerminated
Indicates that an entity’s employment, contract, or ongoing role was ended, typically by a decision from another party rather than by the entity itself.
-
C.
terminatesOn
Indicates that one process, event, or state causes or marks the ending of another at a specific time or condition.
-
D.
typicallyTerminatedIn
Indicates that an event, process, or state usually ends or concludes in a particular way or outcome.
-
E.
stoppedAt
chosen
Indicates that an entity has come to a halt or pause at a specific location or point in time.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1916870148190853874e6cf26bbc7 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.