Triple
T25586286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 28th Street |
E641391
|
entity |
| Predicate | boroughManhattanLine |
P17428
|
FINISHED |
| Object | Lexington Avenue Line |
—
|
NE NERFINISHED |
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: Lexington Avenue Line | Statement: [28th Street, boroughManhattanLine, Lexington Avenue Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boroughManhattanLine Context triple: [28th Street, boroughManhattanLine, Lexington Avenue Line]
-
A.
bronxLine
Indicates a relationship where something is part of, associated with, or runs along the Bronx transit or route line.
-
B.
primaryManhattanLine
Indicates that one line segment or path is the main or dominant axis, measured using Manhattan (grid-based) distance, relative to other possible lines.
-
C.
manhattanTrunkLine
chosen
Indicates a primary or central route, pathway, or connection running through a dense or core area, analogous to a main trunk line in Manhattan.
-
D.
manhattanConnection
Indicates a direct or indirect connection or route between two entities specifically within the Manhattan area or grid.
-
E.
brooklynTerminus
Indicates a relationship where a route, line, or service has its ending point or final stop located in Brooklyn.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9698c3c8190b93af7d959ecd7c1 |
completed | May 2, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:16 p.m.