Triple

T31795382
Position Surface form Disambiguated ID Type / Status
Subject State Transit Authority E811581 entity
Predicate operatedBusServicesIn P39381 FINISHED
Object Sydney metropolitan area 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: Sydney metropolitan area | Statement: [State Transit Authority, operatedBusServicesIn, Sydney metropolitan area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatedBusServicesIn
Context triple: [State Transit Authority, operatedBusServicesIn, Sydney metropolitan area]
  • A. operatesInterurbanBusServices
    Indicates that an entity runs or manages bus transportation services operating between different towns or cities within a region.
  • B. hasBusServices chosen
    Indicates that one location or entity is served by bus routes or bus transportation provided by another.
  • C. operatedPassengerServices
    Indicates that an entity provided and managed transportation services specifically for carrying passengers.
  • D. hasBusServiceOperatorType
    Indicates that a bus service is associated with a specific type or category of operator responsible for running it.
  • E. operatedFreightServiceIn
    Indicates that an entity operated a freight transportation service within or across the specified geographic area or route.
  • 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_69f348e60748819082dcaa7792659803 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69ffc704e1e88190884928a6a5c55a87 completed May 9, 2026, 11:45 p.m.
PD Predicate disambiguation batch_69ffc6b483d881908ad872e25fa6abc5 completed May 9, 2026, 11:43 p.m.
Created at: April 30, 2026, 11:40 p.m.