Triple

T11586415
Position Surface form Disambiguated ID Type / Status
Subject METRO bus rapid transit E274765 entity
Predicate hasPriorityFeature P182 FINISHED
Object transit signal priority on some corridors 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: transit signal priority on some corridors | Statement: [METRO bus rapid transit, hasPriorityFeature, transit signal priority on some corridors]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPriorityFeature
Context triple: [METRO bus rapid transit, hasPriorityFeature, transit signal priority on some corridors]
  • A. hasPrimaryFeature
    Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
  • B. hasFeature chosen
    Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
  • C. hasPriorityAt
    Indicates that one entity holds a specified level of priority or precedence at a particular time, place, or context relative to others.
  • D. hasFeatureCode
    Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
  • E. hasPriorityGroup
    Indicates that one entity is assigned to, or associated with, a specific priority group relative to others.
  • 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_69d6aae6b14c81908dc5a74bad7591f9 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d89462203881908870e991a5b21770 completed April 10, 2026, 6:10 a.m.
PD Predicate disambiguation batch_69d85dcbacd0819094d4a1237055affa completed April 10, 2026, 2:17 a.m.
Created at: April 8, 2026, 9:38 p.m.