Triple

T20796795
Position Surface form Disambiguated ID Type / Status
Subject E train E511931 entity
Predicate connectsWith P37 FINISHED
Object 2 train 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: 2 train | Statement: [E train, connectsWith, 2 train]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 2 train
Context triple: [E train, connectsWith, 2 train]
  • A. 2 train chosen
    The 2 train is a New York City Subway service that runs as a numbered, typically express route on the IRT lines, connecting the Bronx, Manhattan, and Brooklyn.
  • B. 1 train
    The 1 train is a New York City Subway service that runs along the Broadway–Seventh Avenue Line, providing local service between the Bronx and lower Manhattan.
  • C. 5 train
    The 5 train is a New York City Subway service that runs primarily along the IRT Lexington Avenue Line in Manhattan and the Eastern Parkway and Dyre Avenue lines in the Bronx, providing both local and express service.
  • D. 3 train
    The 3 train is a New York City Subway service that runs on the IRT Lenox Avenue and Eastern Parkway Lines, connecting Manhattan and Brooklyn.
  • E. 6 train
    The 6 train is a local New York City Subway service running along the Lexington Avenue Line in Manhattan and into the Bronx.
  • 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_69e0b4cc69f481908e98751e697b9df4 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2ad6f0481909e0bab7119f10f9c completed April 21, 2026, 12:19 a.m.
Created at: April 16, 2026, 12:39 p.m.