Triple
T1060071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenox Avenue Line |
E22885
|
entity |
| Predicate | hasDirectionTerminus |
P15156
|
FINISHED |
| Object | northbound at 145th Street |
—
|
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: northbound at 145th Street | Statement: [Lenox Avenue Line, hasDirectionTerminus, northbound at 145th Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionTerminus Context triple: [Lenox Avenue Line, hasDirectionTerminus, northbound at 145th Street]
-
A.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
B.
lineTerminusDirection
Indicates the directional orientation or bearing at which a line segment or route terminates at its endpoint.
-
C.
hasRouteDirection
chosen
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
-
D.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
E.
terminusType
Indicates the specific kind or role of an endpoint or terminal within a route, network, or 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4ba6e35ac8190802341c31bda0e3b |
completed | March 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69a4b7340a048190807363f19d17a58f |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.