Triple

T666081
Position Surface form Disambiguated ID Type / Status
Subject Heathrow Airport E12863 entity
Predicate hasPublicTransportAccess P3791 FINISHED
Object buses 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: buses | Statement: [Heathrow Airport, hasPublicTransportAccess, buses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPublicTransportAccess
Context triple: [Heathrow Airport, hasPublicTransportAccess, buses]
  • A. hasPublicTransportConnection chosen
    Indicates that there is an available public transportation link or service connecting the related entities.
  • B. hasPublicTransportStop
    Indicates that a location or area contains or is served by a public transport stop, such as a bus, tram, or train stop.
  • C. hasBusStation
    Indicates that a place or area contains or is served by a bus station.
  • D. hasTransportHub
    Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
  • E. hasTransportRoute
    Indicates that there exists a designated transportation connection or route linking one entity to another.
  • 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_69a493355dec819098d4244b2fa34885 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49fd4f4988190a0973ceb7329b4c9 completed March 1, 2026, 8:21 p.m.
PD Predicate disambiguation batch_69a49d16cff881908c8d2c3fe4d1d6fb completed March 1, 2026, 8:09 p.m.
Created at: March 1, 2026, 7:36 p.m.