Triple

T9736799
Position Surface form Disambiguated ID Type / Status
Subject North White Plains E236083 entity
Predicate railLineRole P14634 FINISHED
Object northern terminal for many local Harlem Line trains 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: northern terminal for many local Harlem Line trains | Statement: [North White Plains, railLineRole, northern terminal for many local Harlem Line trains]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railLineRole
Context triple: [North White Plains, railLineRole, northern terminal for many local Harlem Line trains]
  • A. railwayLineRole chosen
    Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
  • B. railNetworkRole
    Indicates the specific function or responsibility an entity has within a rail network system.
  • C. railwayLine
    Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
  • D. railLineOrigin
    Indicates that a rail line begins or originates from a specified location or point.
  • E. railwayLineType
    Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
  • 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_69ca84d313e88190983ee6ffd0ef60d2 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9ef032088190acd94c35b89e48b7 completed April 1, 2026, 10:40 p.m.
PD Predicate disambiguation batch_69cd03c6ffc88190a5e9569e19122ad5 completed April 1, 2026, 11:38 a.m.
Created at: March 30, 2026, 8:22 p.m.