Triple

T10909355
Position Surface form Disambiguated ID Type / Status
Subject SEQM E257652 entity
Predicate replacedCodeForOldAirport P45327 FINISHED
Object SEQU 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: SEQU | Statement: [SEQM, replacedCodeForOldAirport, SEQU]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: replacedCodeForOldAirport
Context triple: [SEQM, replacedCodeForOldAirport, SEQU]
  • A. airportLinkReplaced
    Indicates that one airport rail or transit link has been superseded or taken over in function by another link.
  • B. successorCodeForSameAirport chosen
    Indicates that one code is the direct replacement or follow-up code for the same airport, reflecting a change while the underlying airport remains the same.
  • C. replacedAsMainAirportFor
    Indicates that one airport has taken over the role of being the primary or main airport serving a particular area from another airport.
  • D. airportCodeContext
    Indicates that an airport code is being used or interpreted within a specific contextual framework (such as a region, system, or standard) that defines its meaning.
  • E. previousICAOcode
    Indicates that one entity was the former ICAO (International Civil Aviation Organization) code previously assigned to the other entity.
  • 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_69d6aa8550c8819095508a2ed9acf3db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d77068e5488190bbc881ebf51d6b2e completed April 9, 2026, 9:24 a.m.
PD Predicate disambiguation batch_69d70d3d69e08190bb369e9a7927142c completed April 9, 2026, 2:21 a.m.
Created at: April 8, 2026, 9:22 p.m.