Triple
T9584306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 191st Street (IRT Broadway–Seventh Avenue Line) |
E231248
|
entity |
| Predicate | rankByDepthInNYCSubway |
P89944
|
FINISHED |
| Object | one of the deepest |
—
|
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: one of the deepest | Statement: [191st Street (IRT Broadway–Seventh Avenue Line), rankByDepthInNYCSubway, one of the deepest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankByDepthInNYCSubway Context triple: [191st Street (IRT Broadway–Seventh Avenue Line), rankByDepthInNYCSubway, one of the deepest]
-
A.
rankByPopulationInNYC
Indicates the relative ordering of entities based on the size of their populations within New York City.
-
B.
distanceFromGrandCentral
Indicates the spatial distance between a given entity and Grand Central.
-
C.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
D.
bronxLine
Indicates a relationship where something is part of, associated with, or runs along the Bronx transit or route line.
-
E.
stationBorough
Indicates the borough or administrative district in which a station is located.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99d080c88190a7d3876589d7b864 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:06 p.m.