Triple

T11524933
Position Surface form Disambiguated ID Type / Status
Subject Seoul–Sydney E273267 entity
Predicate servedByFlagCarrierOfAustralia P99947 FINISHED
Object true 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: true | Statement: [Seoul–Sydney, servedByFlagCarrierOfAustralia, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servedByFlagCarrierOfAustralia
Context triple: [Seoul–Sydney, servedByFlagCarrierOfAustralia, true]
  • A. associatedFlagCarrier
    Indicates that one entity serves as the designated national or primary flag carrier airline associated with another entity (such as a country, region, or organization).
  • B. servesAsHubForFlagCarrierOf
    Indicates that a location or facility functions as a primary hub for the national flag carrier airline of a given country or region.
  • C. eligibleCarrier
    Indicates that one entity is a valid or qualified carrier option for another entity under specified conditions.
  • D. isFlagCarrierCodeOf
    Indicates that a given airline code serves as the official flag carrier designation for a particular country or territory.
  • E. wirelessOperator
    Indicates that an entity operates, manages, or provides services for a wireless communication system or network for another entity.
  • 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_69d6aae3fbec8190a14632a5df2538b6 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d87fd379648190b342e0c4b4f685b7 completed April 10, 2026, 4:42 a.m.
PD Predicate disambiguation batch_69d80876e5f0819088cff2e72f773cf6 completed April 9, 2026, 8:13 p.m.
PDg Predicate description generation batch_69d822ef46988190a1c360da4ee14fef completed April 9, 2026, 10:06 p.m.
Created at: April 8, 2026, 9:37 p.m.