Triple

T3177812
Position Surface form Disambiguated ID Type / Status
Subject Veer Savarkar International Airport E66506 entity
Predicate hasIATACode P2569 FINISHED
Object IXZ E66506 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: IXZ | Statement: [Veer Savarkar International Airport, hasIATACode, IXZ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IXZ
Context triple: [Veer Savarkar International Airport, hasIATACode, IXZ]
  • A. IXZ chosen
    IXZ is the IATA airport code for Veer Savarkar International Airport serving Port Blair in the Andaman and Nicobar Islands, India.
  • B. IX
    IX is the stock ticker symbol for Orix Corporation, a major Japanese financial services and leasing company listed on the New York Stock Exchange.
  • C. KIX
    KIX is the three-letter IATA airport code for Kansai International Airport serving the Osaka region of Japan.
  • D. l’X
    l’X is the traditional nickname of École Polytechnique, France’s elite engineering grande école renowned for its rigorous scientific education and prestigious alumni.
  • E. IXS
    IXS is the three-letter IATA airport code assigned to Silchar Airport in Assam, India.
  • 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_69ad8586a34c8190944c63ec11a8de1a completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada69c2edc81908bfd23a1d5ce970e completed March 8, 2026, 4:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69b235f5ace88190b6bd16ec240240c0 completed March 12, 2026, 3:41 a.m.
Created at: March 8, 2026, 3:06 p.m.