Triple
T8018579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q line |
E186681
|
entity |
| Predicate | reached96thStreetSecondAvenue |
P80593
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Q line, reached96thStreetSecondAvenue, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reached96thStreetSecondAvenue Context triple: [Q line, reached96thStreetSecondAvenue, 2017]
-
A.
primaryAvenueInManhattan
Indicates that one entity is the main or most significant avenue located within Manhattan in relation to the other entity.
-
B.
hasSecondaryStreet
Indicates that an entity is associated with an additional, non-primary street address or roadway.
-
C.
bronxLine
Indicates a relationship where something is part of, associated with, or runs along the Bronx transit or route line.
-
D.
brooklynTerminus
Indicates a relationship where a route, line, or service has its ending point or final stop located in Brooklyn.
-
E.
avenueRadiatingFrom
Indicates that one avenue extends outward from and is oriented away from another central point or thoroughfare, like a spoke radiating from a hub.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df626e8819098a9f8908dfdad3b |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:20 p.m.