Triple

T8630817
Position Surface form Disambiguated ID Type / Status
Subject BCS3 E204395 entity
Predicate icaoCodeType P84521 FINISHED
Object four‑character aircraft type designator 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: four‑character aircraft type designator | Statement: [BCS3, icaoCodeType, four‑character aircraft type designator]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: icaoCodeType
Context triple: [BCS3, icaoCodeType, four‑character aircraft type designator]
  • A. ICAOcode
    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. hasIATAcode
    Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
  • 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. hasAirportCodeType
    Indicates that an airport code is associated with a specific classification or type (e.g., IATA, ICAO, FAA).
  • 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_69ca834b903c8190add96cc651e1a477 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5730309081909a9a0256c9bf5f8f completed March 31, 2026, 11:22 p.m.
PD Predicate disambiguation batch_69cc455906f8819082edd79cb4a1cf28 completed March 31, 2026, 10:06 p.m.
PDg Predicate description generation batch_69cc572d99bc819097f36b140c2ee1ce completed March 31, 2026, 11:22 p.m.
Created at: March 30, 2026, 6:27 p.m.