Triple
T25682358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steeles Avenue East |
E643973
|
entity |
| Predicate | hasEasternTerminusNear |
P3569
|
FINISHED |
| Object | York–Durham Line |
—
|
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: York–Durham Line | Statement: [Steeles Avenue East, hasEasternTerminusNear, York–Durham Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEasternTerminusNear Context triple: [Steeles Avenue East, hasEasternTerminusNear, York–Durham Line]
-
A.
easternTerminusLocatedOn
Indicates that the eastern endpoint of a route, line, or path is situated on or at a specified feature or location.
-
B.
easternTerminusTown
Indicates that a given town serves as the eastern endpoint or terminus of a route, line, or corridor.
-
C.
easternTerminusRegion
Indicates the region in which something (such as a route, line, or path) has its eastern endpoint or terminus.
-
D.
terminusEast
chosen
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
-
E.
hasSouthernTerminus
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb7a1bc48190977f41d62801e190 |
completed | May 2, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 8:02 p.m.