Triple

T28249981
Position Surface form Disambiguated ID Type / Status
Subject IRT (A Division) lines E712285 entity
Predicate fareControlledBy P1740 FINISHED
Object Metropolitan Transportation Authority NE NERFINISHED

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: Metropolitan Transportation Authority | Statement: [IRT (A Division) lines, fareControlledBy, Metropolitan Transportation Authority]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareControlledBy
Context triple: [IRT (A Division) lines, fareControlledBy, Metropolitan Transportation Authority]
  • A. fareControl chosen
    Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
  • B. fareControlUnifiedWith
    Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
  • C. fareControlLocation
    Indicates a location where access to or use of a transportation service is regulated, checked, or controlled for fare payment.
  • D. isUnderControlOf
    Indicates that one entity is subject to the authority, direction, or governance of another entity.
  • E. railwayControlledBy
    Indicates that the operation, management, or authority over a railway is exercised by a specified controlling entity.
  • 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_69efb51fb98881909692421959ec0170 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f643eecbe481908f4c9be0fa878f36 completed May 2, 2026, 6:35 p.m.
PD Predicate disambiguation batch_69f641e0fde08190bf06a1c5b388aa84 completed May 2, 2026, 6:26 p.m.
Created at: April 27, 2026, 11:04 p.m.