Triple

T38344666
Position Surface form Disambiguated ID Type / Status
Subject IRT Division (limited connections and yards only) E1041505 entity
Predicate hasPhysicalSeparationFrom P96091 FINISHED
Object most IND/BMT mainline tracks 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: most IND/BMT mainline tracks | Statement: [IRT Division (limited connections and yards only), hasPhysicalSeparationFrom, most IND/BMT mainline tracks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPhysicalSeparationFrom
Context triple: [IRT Division (limited connections and yards only), hasPhysicalSeparationFrom, most IND/BMT mainline tracks]
  • A. hasCompanionSeparation
    Indicates that one entity is separated or kept apart from its companion or associated counterpart.
  • B. geographicallySeparatedFrom chosen
    Indicates that two places or regions are distinct and apart from each other in physical location or geographic space.
  • C. laterSeparatedFrom
    Indicates that one entity became separated from another at a later time than some referenced separation event.
  • D. definedSeparationFrom
    Indicates a formally specified distinction or boundary established between one entity and another.
  • E. wouldHaveBeenSeparatedFrom
    Indicates a hypothetical or counterfactual situation in which one entity would have been divided, detached, or kept apart from another entity if certain conditions had occurred.
  • 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_69f76e2ad95481908c920c0e5c1c3e26 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fd0d0ba5c48190bddb3f0e6637544c completed May 7, 2026, 10:07 p.m.
PD Predicate disambiguation batch_69fd0c4324a8819086c90adf46216e0e completed May 7, 2026, 10:03 p.m.
Created at: May 3, 2026, 4:30 p.m.