Triple

T18427081
Position Surface form Disambiguated ID Type / Status
Subject B Division (New York City Subway) E450167 entity
Predicate hasPlatformClearances P131559 FINISHED
Object designed for wider cars 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: designed for wider cars | Statement: [B Division (New York City Subway), hasPlatformClearances, designed for wider cars]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPlatformClearances
Context triple: [B Division (New York City Subway), hasPlatformClearances, designed for wider cars]
  • A. hasClearance
    Indicates that one entity possesses the required authorization level or permission to access or perform actions on another entity or resource.
  • B. hasNavigationClearance
    Indicates that an entity has been granted authorization to navigate through a specified area or along a particular route.
  • C. hasBridgeClearance
    Indicates that there is a specified vertical clearance available beneath a bridge for passing objects or vehicles.
  • D. hasClearanceBelow
    Indicates that one entity’s clearance level is lower than another entity’s clearance level.
  • E. clearanceRequired
    Indicates that a specific level of authorization or security clearance is needed before the related action can be performed or access can be granted.
  • 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_69d8d381d6388190a9e94e9c658174e4 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e51b13ee88819091e7e007d17dcc73 completed April 19, 2026, 6:12 p.m.
PD Predicate disambiguation batch_69e469bf7f74819096a01173493412c2 completed April 19, 2026, 5:35 a.m.
PDg Predicate description generation batch_69e46d2aa72c8190a40854a7a52081e2 completed April 19, 2026, 5:50 a.m.
Created at: April 10, 2026, 11:25 a.m.