Triple
T369677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 2 Bloor–Danforth |
E8239
|
entity |
| Predicate | isUndergroundIn |
P10157
|
FINISHED |
| Object | central Toronto |
—
|
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: central Toronto | Statement: [Line 2 Bloor–Danforth, isUndergroundIn, central Toronto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUndergroundIn Context triple: [Line 2 Bloor–Danforth, isUndergroundIn, central Toronto]
-
A.
locatedUnder
chosen
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
B.
hasBasement
Indicates that a building or structure includes a basement level as part of its physical layout.
-
C.
usedInCity
Indicates that something is utilized, applied, or operates within the context or boundaries of a particular city.
-
D.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
E.
hasShuttleLine
Indicates that there is a shuttle service or route operating between the related 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebfdb0608190b1794a871d0d237a |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e960d880819084b3df4e5137a1e2 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.