Triple

T32883175
Position Surface form Disambiguated ID Type / Status
Subject Metropolitan Transit Corporation E841122 entity
Predicate operatedBusRoutes P70721 FINISHED
Object local bus routes in King County 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: local bus routes in King County | Statement: [Metropolitan Transit Corporation, operatedBusRoutes, local bus routes in King County]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatedBusRoutes
Context triple: [Metropolitan Transit Corporation, operatedBusRoutes, local bus routes in King County]
  • A. operatedRoutes chosen
    Indicates that an agent (such as a company or organization) runs or manages specific routes, typically providing services along those paths.
  • B. operatesInterurbanBusServices
    Indicates that an entity runs or manages bus transportation services operating between different towns or cities within a region.
  • C. hasBusServices
    Indicates that one location or entity is served by bus routes or bus transportation provided by another.
  • D. busSystemName
    Indicates that a bus system is identified or referred to by a specific name.
  • E. servedByBusCorridor
    Indicates that a location or route is provided public transport service by a specific bus corridor.
  • 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_69f349446e288190a70c05bcc4d81172 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_6a0031ed5d708190ab93516ad081ada6 completed May 10, 2026, 7:21 a.m.
PD Predicate disambiguation batch_6a0031b5dbd081908eb0f4dbb8a0eac3 completed May 10, 2026, 7:20 a.m.
Created at: May 1, 2026, 1:18 a.m.