Triple

T6356442
Position Surface form Disambiguated ID Type / Status
Subject Beverly Road E143003 entity
Predicate servedBy P82 FINISHED
Object 5 train E11881 NE 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: 5 train | Statement: [Beverly Road, servedBy, 5 train]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 5 train
Context triple: [Beverly Road, servedBy, 5 train]
  • A. 5 train chosen
    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.
  • B. 4 train
    The 4 train is a New York City Subway service that runs along the Lexington Avenue Line in Manhattan, providing express service between the Bronx and Brooklyn.
  • C. 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.
  • D. 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.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69c008d7a9c4819098d647ec47776917 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c067f37d0881909289bafb09e29298 completed March 22, 2026, 10:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69c63869ef148190816b152f2724de49 completed March 27, 2026, 7:57 a.m.
Created at: March 22, 2026, 4:32 p.m.