Triple

T18990698
Position Surface form Disambiguated ID Type / Status
Subject B (New York City Subway service) E464673 entity
Predicate routeThroughBronx P21450 FINISHED
Object via IND Concourse Line 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: via IND Concourse Line | Statement: [B (New York City Subway service), routeThroughBronx, via IND Concourse Line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: routeThroughBronx
Context triple: [B (New York City Subway service), routeThroughBronx, via IND Concourse Line]
  • A. bronxLine
    Indicates a relationship where something is part of, associated with, or runs along the Bronx transit or route line.
  • B. bronxLocalStops
    Indicates that something (typically a train or service) makes local, non-express stops within the Bronx.
  • C. connectsRockawayParkTo
    Indicates a relationship where something serves as a link or route between Rockaway Park and another place or entity.
  • D. manhattanTrunkLine
    Indicates a primary or central route, pathway, or connection running through a dense or core area, analogous to a main trunk line in Manhattan.
  • E. passesThroughBorough chosen
    Indicates that something (such as a route, line, or path) traverses or goes through a particular borough.
  • F. None of above.

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_69d8dd01a56c81909694a128c66b21d7 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6632cb08190a28f6ab74c2156d8 completed April 20, 2026, 7:31 a.m.
PD Predicate disambiguation batch_69e4a2f88e0c81908cb20f08bf24cd32 completed April 19, 2026, 9:40 a.m.
Created at: April 10, 2026, 12:01 p.m.