Triple

T19287665
Position Surface form Disambiguated ID Type / Status
Subject Klynveld Main Goerdeler E482355 entity
Predicate hasAbbreviation P43 FINISHED
Object KMG NE NERFINISHED

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: KMG | Statement: [Klynveld Main Goerdeler, hasAbbreviation, KMG]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KMG
Context triple: [Klynveld Main Goerdeler, hasAbbreviation, KMG]
  • A. KMG
    KMG is the IATA airport code for Kunming Changshui International Airport, a major air transport hub serving Kunming in Yunnan Province, China.
  • B. KMG chosen
    KMG was the stock ticker symbol for Kerr-McGee Oil Industries, a former American energy company involved in oil and gas exploration and production.
  • C. KGM
    KGM is the three-letter National Rail station code assigned to Kingham railway station in Oxfordshire, England.
  • D. KGM
    KGM is the Turkish General Directorate of Highways, the national authority responsible for planning, constructing, and maintaining Turkey’s road network.
  • E. KMKG
    KMKG is the ICAO airport code for Muskegon County Airport in Muskegon, Michigan, United States.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8cf61b0819096fe3e4107827c4e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fc032f108190a89e47d1458f3f55 completed April 20, 2026, 10:12 a.m.
Created at: April 10, 2026, 1:30 p.m.