Triple

T1180106
Position Surface form Disambiguated ID Type / Status
Subject Pelham Line E25114 entity
Predicate hasThroughServiceWith P26302 FINISHED
Object Brooklyn via IRT Lexington Avenue Line trunk and Brooklyn branches 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: Brooklyn via IRT Lexington Avenue Line trunk and Brooklyn branches | Statement: [Pelham Line, hasThroughServiceWith, Brooklyn via IRT Lexington Avenue Line trunk and Brooklyn branches]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasThroughServiceWith
Context triple: [Pelham Line, hasThroughServiceWith, Brooklyn via IRT Lexington Avenue Line trunk and Brooklyn branches]
  • A. hasServiceTo
    Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
  • B. hasServiceType
    Indicates that an entity is associated with or categorized by a particular type of service.
  • C. hasServiceOnCorridor
    Indicates that a service operates along, or is provided on, a specific corridor or route.
  • D. servedByService
    Indicates that something is provided, handled, or fulfilled by a particular service.
  • E. hasServiceClass
    Indicates that an entity is associated with, or categorized under, a particular class or type of service.
  • F. None of above. chosen

Provenance (4 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_69a494267b4c819088c97a59182bf56a completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bd53e4b48190abb2167f8074a6bc completed March 1, 2026, 10:27 p.m.
PD Predicate disambiguation batch_69a4bb5844348190b01ac6506906ba3b completed March 1, 2026, 10:19 p.m.
PDg Predicate description generation batch_69a4bd52177081908c5cec8e731b836e completed March 1, 2026, 10:27 p.m.
Created at: March 1, 2026, 7:45 p.m.