Triple

T16961008
Position Surface form Disambiguated ID Type / Status
Subject ICAO airport code system E411425 entity
Predicate regionPrefixExample P34409 FINISHED
Object K for contiguous United States 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: K for contiguous United States | Statement: [ICAO airport code system, regionPrefixExample, K for contiguous United States]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionPrefixExample
Context triple: [ICAO airport code system, regionPrefixExample, K for contiguous United States]
  • A. addressExamplePrefix
    Indicates that an address example is introduced or categorized by a specific prefix string used to distinguish or group it.
  • B. addressPrefix
    Indicates that one address string serves as the starting portion or leading segment of another address.
  • C. registrationPrefix
    Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
  • D. namespacePrefix
    Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier system.
  • E. icaoRegionPrefix chosen
    Indicates the regional ICAO prefix that designates the geographic or administrative region associated with an aviation-related 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_69d886c9c9d481909afe222093641cae completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d0209a9081909d9c62456bc16e14 completed April 18, 2026, 6:40 p.m.
PD Predicate disambiguation batch_69e32b9cddf88190bc42709604047353 completed April 18, 2026, 6:58 a.m.
Created at: April 10, 2026, 5:31 a.m.