Triple
T968483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RideKC Streetcar |
E20890
|
entity |
| Predicate | plannedExtensionLength |
P22512
|
FINISHED |
| Object | about 3.5 miles |
—
|
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: about 3.5 miles | Statement: [RideKC Streetcar, plannedExtensionLength, about 3.5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedExtensionLength Context triple: [RideKC Streetcar, plannedExtensionLength, about 3.5 miles]
-
A.
plannedExtensionDirection
Indicates the intended directional path or orientation along which something is planned to be extended in the future.
-
B.
possibleLengthDays
Indicates that an entity can have a duration, measured in whole or fractional days, equal to the specified value.
-
C.
missionExtension
Indicates that an existing mission is being prolonged beyond its originally planned duration or scope.
-
D.
missionDurationPlanned
Indicates the length of time that a mission is scheduled or intended to last according to its plan.
-
E.
extendedBy
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4481f508190adcf0a965a23862c |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a579888190afb489ac9fe8391c |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b385176081909e3e8c3f647c1fd4 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.