Triple
T17318168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Line (Montreal Metro) |
E420483
|
entity |
| Predicate | plannedExtensionStatus |
P40548
|
FINISHED |
| Object | under development |
—
|
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: under development | Statement: [Blue Line (Montreal Metro), plannedExtensionStatus, under development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedExtensionStatus Context triple: [Blue Line (Montreal Metro), plannedExtensionStatus, under development]
-
A.
plannedExtensionTo
Indicates that one entity is intended or scheduled to be extended, expanded, or continued by another entity in the future.
-
B.
plannedExtensionLength
Indicates the intended or proposed length of an extension as specified in a plan or design.
-
C.
plannedExtensionDirection
Indicates the intended directional path or orientation along which something is planned to be extended in the future.
-
D.
plannedExtensionProvince
Indicates that a planned extension or expansion is intended to occur within the specified province.
-
E.
expansionStatus
chosen
Indicates the current state or phase of growth, enlargement, or extension of something relative to its previous or intended size or scope.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399ea7dc8190a0ecab7534fe16c3 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.