Triple
T369654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 2 Bloor–Danforth |
E8239
|
entity |
| Predicate | hasLineNumber |
P11728
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Line 2 Bloor–Danforth, hasLineNumber, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineNumber Context triple: [Line 2 Bloor–Danforth, hasLineNumber, 2]
-
A.
hasNumberOfLines
Indicates the relationship that specifies how many lines are associated with a given entity.
-
B.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
C.
containsLine
Indicates that one entity includes or encloses a specific line within its spatial or structural extent.
-
D.
hasSignalLine
Indicates that one entity is connected to another by a signal-carrying line or path used for transmitting information or control signals.
-
E.
hasMainTrunkLine
Indicates that an entity is connected to or served by a primary or central trunk line within a network or system.
- F. None of above. chosen
Provenance (4 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_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0b23ec8190bef9d593162388a4 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.