Triple
T10142478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro D Line |
E231618
|
entity |
| Predicate | extensionDirection |
P19358
|
FINISHED |
| Object | westward along Wilshire Boulevard |
—
|
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: westward along Wilshire Boulevard | Statement: [Metro D Line, extensionDirection, westward along Wilshire Boulevard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extensionDirection Context triple: [Metro D Line, extensionDirection, westward along Wilshire Boulevard]
-
A.
plannedExtensionDirection
chosen
Indicates the intended directional path or orientation along which something is planned to be extended in the future.
-
B.
extension
Indicates that one entity is a lengthening, continuation, or added part of another entity beyond its original limits.
-
C.
extensionTerminus
Indicates the endpoint or final limit to which something is extended or continues.
-
D.
extendedFrom
Indicates that one entity is derived by adding to or building upon the scope, content, or structure of another entity.
-
E.
extensionPotential
Indicates the potential or likelihood that an existing arrangement, contract, or state will be extended beyond its current term 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdeb273fec8190818707167e031d58 |
completed | April 2, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:07 p.m.