Triple

T16910962
Position Surface form Disambiguated ID Type / Status
Subject IND lines E410191 entity
Predicate servicePatternInfluenced P125188 FINISHED
Object lettered route designations in NYC Subway 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: lettered route designations in NYC Subway | Statement: [IND lines, servicePatternInfluenced, lettered route designations in NYC Subway]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servicePatternInfluenced
Context triple: [IND lines, servicePatternInfluenced, lettered route designations in NYC Subway]
  • A. servicePatternComplement
    Indicates that one service pattern functions as a complement to another, covering routes, times, or conditions that the other pattern does not.
  • B. servicePatternType
    Indicates the type or category of service pattern that characterizes how a service is structured, scheduled, or delivered.
  • C. servicePatternOf
    Indicates that one entity is the service pattern (e.g., schedule, routing, or operational configuration) that defines or characterizes how another service-related entity operates.
  • D. serviceWith
    Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
  • E. currentServicePatternIntroduced
    Indicates that the currently operating service pattern was first implemented or put into effect at a specific point in time.
  • 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_69d886c7b1e481908c3766dfa8c13458 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3ca3ca0c481909ff361ccf4a922e3 completed April 18, 2026, 6:15 p.m.
PD Predicate disambiguation batch_69e32b9489408190bcb2ede567ff5bf9 completed April 18, 2026, 6:58 a.m.
PDg Predicate description generation batch_69e34fb7c8c8819086975b7955b7d8ef completed April 18, 2026, 9:32 a.m.
Created at: April 10, 2026, 5:30 a.m.