Triple

T3847793
Position Surface form Disambiguated ID Type / Status
Subject ZBAD E85214 entity
Predicate IATAcode P418 FINISHED
Object PKX E85213 NE 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: PKX | Statement: [ZBAD, IATAcode, PKX]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PKX
Context triple: [ZBAD, IATAcode, PKX]
  • A. PKX chosen
    PKX is the IATA airport code for Beijing Daxing International Airport, a major international aviation hub serving Beijing, China.
  • B. PK
    PK is the two-letter ISO 3166-1 alpha-2 country code that uniquely identifies Pakistan in international standards and systems.
  • C. PNX
    PNX is the IATA airport code for North Texas Regional Airport, a public airport serving the Sherman–Denison area in Texas, United States.
  • D. PKT
    PKT is the time zone used throughout Pakistan, corresponding to UTC+5 hours.
  • E. PIK
    PIK is a leading German research institute focused on analyzing the causes and impacts of climate change and developing strategies for sustainable solutions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69aed936de1c81908f91bed80f70abb2 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeebcc8a0481909c35161336bdfbf9 completed March 9, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69b50414acdc81909bf0b62afa3fe536 completed March 14, 2026, 6:45 a.m.
Created at: March 9, 2026, 3:18 p.m.