Triple
T20812639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 3 Eglinton (planned) |
E512350
|
entity |
| Predicate | hasPlannedMode |
P140445
|
FINISHED |
| Object | rapid transit |
—
|
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: rapid transit | Statement: [Line 3 Eglinton (planned), hasPlannedMode, rapid transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedMode Context triple: [Line 3 Eglinton (planned), hasPlannedMode, rapid transit]
-
A.
plannedMode
chosen
Indicates that a particular mode, method, or state has been intentionally selected or scheduled in advance for use.
-
B.
hasPlannedPart
Indicates that one entity includes another entity as a component or segment within a planned or scheduled whole.
-
C.
hasPlanningPattern
Indicates that an entity follows or is associated with a particular planning pattern or structured approach to planning.
-
D.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
E.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d415688190b66adc44d4df9bbb |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.