Triple

T9284403
Position Surface form Disambiguated ID Type / Status
Subject AmericanConnection E223150 entity
Predicate ICAOCodeUsed P419 FINISHED
Object various codes of operating carriers — 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: various codes of operating carriers | Statement: [AmericanConnection, ICAOCodeUsed, various codes of operating carriers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ICAOCodeUsed
Context triple: [AmericanConnection, ICAOCodeUsed, various codes of operating carriers]
  • A. ICAOcode chosen
    Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
  • B. IATAcode
    Indicates the three-letter IATA airport or airline code assigned to the entity.
  • C. icaoCodeType
    Indicates that the relationship specifies or classifies the ICAO (International Civil Aviation Organization) code associated with an entity.
  • D. hasIATAcode
    Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
  • 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_69ca842123588190b3f2e1a69037d141 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd081e72988190917f425e64631837 completed April 1, 2026, 11:57 a.m.
PD Predicate disambiguation batch_69cc7a576ec88190bbb787eb82e2e539 completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:34 p.m.