Triple
T1459248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1900 Yonge Street |
E31471
|
entity |
| Predicate | servedByTransitMode |
P14525
|
FINISHED |
| Object | subway |
—
|
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: subway | Statement: [1900 Yonge Street, servedByTransitMode, subway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByTransitMode Context triple: [1900 Yonge Street, servedByTransitMode, subway]
-
A.
transportationServedBy
chosen
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
B.
appliesToTransitSystem
Indicates that something (such as a rule, policy, feature, or condition) is relevant or applicable to a particular transit or transportation system.
-
C.
hasPublicTransitProvider
Indicates that a place or region is served by a specific public transit operating organization or agency.
-
D.
partOfTransitSystem
Indicates that something is a component or segment within a larger transit or transportation system.
-
E.
appliesToTransitLine
Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular transit line.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59c1c288190be08064f2d351b2b |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.