Triple

T6600374
Position Surface form Disambiguated ID Type / Status
Subject McCoy Air Force Base E148980 entity
Predicate legacyPreservedIn P16342 FINISHED
Object IATA airport code MCO 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: IATA airport code MCO | Statement: [McCoy Air Force Base, legacyPreservedIn, IATA airport code MCO]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legacyPreservedIn
Context triple: [McCoy Air Force Base, legacyPreservedIn, IATA airport code MCO]
  • A. retainsHeritageOf chosen
    Indicates that one entity preserves, maintains, or keeps alive the cultural, historical, or traditional legacy originating from another entity.
  • B. selectedForPreservationBy
    Indicates that one entity has been chosen by another entity to be kept, maintained, or safeguarded from removal or loss.
  • C. stateOfPreservation
    Indicates the condition or degree to which something has been maintained, conserved, or kept intact over time.
  • D. hasSubjectOfPreservation
    Indicates that something is the specific focus or object being preserved or conserved within a preservation relationship.
  • E. preservedExample
    Indicates that an example instance has been kept intact or maintained in its original state for future reference or use.
  • 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_69c687eaa7508190bb58ce2aa02039b3 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6cc9c6cb0819084fec8e0beb430de completed March 27, 2026, 6:29 p.m.
PD Predicate disambiguation batch_69c6acfd17388190bd0bb8b2371e7df1 completed March 27, 2026, 4:14 p.m.
Created at: March 27, 2026, 1:56 p.m.