Triple

T25715360
Position Surface form Disambiguated ID Type / Status
Subject London–Sydney E644847 entity
Predicate typicalEndAirport P194595 FINISHED
Object Sydney Kingsford Smith Airport 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 Kingsford Smith Airport | Statement: [London–Sydney, typicalEndAirport, Sydney Kingsford Smith Airport]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalEndAirport
Context triple: [London–Sydney, typicalEndAirport, Sydney Kingsford Smith Airport]
  • A. typicalDestinationAirportIATA
    Indicates the IATA airport code that is typically the destination in this kind of trip or route.
  • B. typicalOriginAirportIATA
    Indicates the usual or primary origin airport for an entity, identified by its IATA airport code.
  • C. destinationAirportICAO
    Indicates the airport, identified by its ICAO code, that serves as the destination in a flight or travel-related context.
  • D. destinationAirportLocation
    Indicates the geographic location associated with the airport that serves as the destination in a trip or flight.
  • E. destinationAirportInvestigated
    Indicates that an airport serving as a destination has been examined or analyzed, typically as part of an investigation or assessment process.
  • F. None of above. chosen

Provenance (4 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_69e77e8476fc8190bd5e9d05b89fad0a completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69fd7e364a648190a1e9e1d9fc76e99e completed May 8, 2026, 6:09 a.m.
PD Predicate disambiguation batch_69fd7bb547608190a3b04dddbca6b8bc completed May 8, 2026, 5:59 a.m.
PDg Predicate description generation batch_69fd7e35967081909f8bc8389d976ffd completed May 8, 2026, 6:09 a.m.
Created at: April 21, 2026, 9:40 p.m.