Triple
T7141406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Line Northwest Extension corridor |
E166449
|
entity |
| Predicate | plannedDirection |
P19358
|
FINISHED |
| Object | northwest |
—
|
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: northwest | Statement: [Red Line Northwest Extension corridor, plannedDirection, northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedDirection Context triple: [Red Line Northwest Extension corridor, plannedDirection, northwest]
-
A.
plannedExtensionDirection
chosen
Indicates the intended directional path or orientation along which something is planned to be extended in the future.
-
B.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
C.
plannedTarget
Indicates that one entity has been designated or selected as the intended target or objective of another entity’s planned action or operation.
-
D.
directedTo
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
-
E.
plannedLocation
Indicates the intended or scheduled location where an entity is expected to be or an event is planned to occur.
- 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e778875c8190a5202d3efe5a842d |
completed | March 27, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.