Triple

T27238073
Position Surface form Disambiguated ID Type / Status
Subject BZE E687120 entity
Predicate hasGroundTransportationOption P1298 FINISHED
Object taxis 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: taxis | Statement: [BZE, hasGroundTransportationOption, taxis]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGroundTransportationOption
Context triple: [BZE, hasGroundTransportationOption, taxis]
  • A. hasGroundTransportation chosen
    Indicates that an entity provides, includes, or is connected to transportation services or options that operate on land (e.g., cars, buses, trains).
  • B. hasTransportRoute
    Indicates that there exists a designated transportation connection or route linking one entity to another.
  • C. hasTransportationElement
    Indicates that one entity includes, involves, or is associated with a specific transportation-related component or feature.
  • D. hasBoardingOption
    Indicates that an entity offers or is associated with a particular way or method by which passengers or items can board or be taken on.
  • E. hasTransportationAbove
    Indicates that one entity provides or has transportation infrastructure or services located above another entity (e.g., elevated roads, railways, or transit lines).
  • 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_69ef355547408190b5ca0d777c65040a completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f66c5c13808190887180099745673b completed May 2, 2026, 9:27 p.m.
PD Predicate disambiguation batch_69f66abddc448190a488852f8abdeb2c completed May 2, 2026, 9:21 p.m.
Created at: April 27, 2026, 10:35 a.m.