Triple

T37587133
Position Surface form Disambiguated ID Type / Status
Subject 170th Street E935148 entity
Predicate hasDaytimeLocalService P112159 FINISHED
Object B and D 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: B and D trains | Statement: [170th Street, hasDaytimeLocalService, B and D trains]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDaytimeLocalService
Context triple: [170th Street, hasDaytimeLocalService, B and D trains]
  • A. daytimeLocalService chosen
    Indicates that a service operates or is available during daytime hours in the local time of the relevant location.
  • B. hasLocalService
    Indicates that one entity provides or is associated with a service that operates within the local area or vicinity of another entity.
  • C. hasLocalityDay
    Indicates that a specific day is officially designated or observed within a particular locality or municipality.
  • D. hasWeekdayService
    Indicates that a service operates on weekdays (typically Monday through Friday).
  • E. hasTimeOfDay
    Indicates that a situation, event, or state occurs during, or is associated with, a specific part of the day (e.g., morning, afternoon, evening, night).
  • 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_69f76ece61dc8190a0ab33f8d87d0a7e completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbacaf54648190811ea33b34907e8e completed May 6, 2026, 9:03 p.m.
PD Predicate disambiguation batch_69fba883f770819091059c6f6c6af9f7 completed May 6, 2026, 8:45 p.m.
Created at: May 3, 2026, 4:17 p.m.