Triple

T18894282
Position Surface form Disambiguated ID Type / Status
Subject New York City Subway 1 line E462169 entity
Predicate servesStation P839 FINISHED
Object 191st 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: 191st Street | Statement: [New York City Subway 1 line, servesStation, 191st Street]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 191st Street
Context triple: [New York City Subway 1 line, servesStation, 191st Street]
  • A. 191st Street chosen
    191st Street is a deep-level New York City Subway station in Washington Heights, Manhattan, known for its long pedestrian tunnel and elevator access to the 1 train.
  • B. 190th Street
    190th Street is a deep-level New York City Subway station in Washington Heights, Manhattan, served by the A train.
  • C. 181st Street
    181st Street is a New York City Subway station in Washington Heights serving the IND Eighth Avenue Line.
  • D. 231st Street
    231st Street is a New York City Subway station in the Bronx on the IRT Broadway–Seventh Avenue Line.
  • E. 91st Street
    91st Street is a numbered urban thoroughfare commonly found in grid-based city layouts, such as those in New York City.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dcfd05bc819088903cca13cc2846 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c47dfa8c8190940858a010129d13 completed April 20, 2026, 6:15 a.m.
Created at: April 10, 2026, 11:58 a.m.