Triple

T30183131
Position Surface form Disambiguated ID Type / Status
Subject Metrobus routes E767258 entity
Predicate operatingAgencyType P120763 FINISHED
Object public transit agency 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: public transit agency | Statement: [Metrobus routes, operatingAgencyType, public transit agency]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatingAgencyType
Context triple: [Metrobus routes, operatingAgencyType, public transit agency]
  • A. managingAgencyAbbreviation
    Indicates that one entity is identified by the abbreviated name of the agency responsible for managing or overseeing it.
  • B. transitAgencyType chosen
    Indicates the classification or category of a transit agency based on the type of transportation services it provides.
  • C. regulatingAgency
    Indicates that one entity serves as the official authority responsible for overseeing, controlling, or enforcing rules and standards on another entity or activity.
  • D. agencyTypeOfOperator
    Indicates the specific type or category of agency to which the operator belongs or by which the operator is characterized.
  • E. mainImplementingAgency
    Indicates which agency has primary responsibility for implementing a given project, program, or policy.
  • 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_69f2247cc3d88190811dec3face94bf5 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69ff49016dcc8190a8a43868c728b4f1 completed May 9, 2026, 2:47 p.m.
PD Predicate disambiguation batch_69ff4891924c8190b5be340e2520e012 completed May 9, 2026, 2:45 p.m.
Created at: April 29, 2026, 7:26 p.m.