Triple
T25527903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7 |
E639824
|
entity |
| Predicate | formerManhattanTerminus |
P176685
|
FINISHED |
| Object | Times Square–42nd Street |
—
|
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: Times Square–42nd Street | Statement: [7, formerManhattanTerminus, Times Square–42nd Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerManhattanTerminus Context triple: [7, formerManhattanTerminus, Times Square–42nd Street]
-
A.
terminusInManhattan
Indicates that the endpoint or final stop of something (such as a route, line, or service) is located within Manhattan.
-
B.
brooklynTerminus
Indicates a relationship where a route, line, or service has its ending point or final stop located in Brooklyn.
-
C.
isNorthernManhattanTerminalFor
Indicates that one location serves as the northern Manhattan terminal endpoint for a specified transit line or route.
-
D.
terminusBorough
Indicates the borough in which the endpoint or terminus of something (such as a route or line) is located.
-
E.
lateNightManhattanTerminal
Indicates a terminal or endpoint that operates or is specifically used in Manhattan during late-night hours.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 21, 2026, 3:11 p.m.