Triple
T19837935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 14th Street–Eighth Avenue |
E476646
|
entity |
| Predicate | openedAsBMTCanarsieTerminal |
P137523
|
FINISHED |
| Object | 1931 |
—
|
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: 1931 | Statement: [14th Street–Eighth Avenue, openedAsBMTCanarsieTerminal, 1931]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsBMTCanarsieTerminal Context triple: [14th Street–Eighth Avenue, openedAsBMTCanarsieTerminal, 1931]
-
A.
openedAsNYCSubwayStation
Indicates that an entity began operation specifically as a New York City Subway station at the time it opened.
-
B.
openedAsMetroNorthService
Indicates that a transportation facility or line began operation specifically as part of the Metro-North Railroad service.
-
C.
openedAsPartOfNJTransit
Indicates that the subject entity was opened specifically as a component or facility of the NJ Transit system.
-
D.
openedAsSubway
Indicates that a transportation facility or line originally began operation specifically as a subway service.
-
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. 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65802f57081909e4e94694684bda4 |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:50 p.m.