Triple
T3273016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Blair Airport |
E68693
|
entity |
| Predicate | IATAcode |
P418
|
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: [Port Blair Airport, IATAcode, IXZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IXZ Context triple: [Port Blair Airport, IATAcode, 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff6308881908886a44804a0bb09 |
completed | March 8, 2026, 5:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b28f0793e08190af55ee16e5091451 |
completed | March 12, 2026, 10:01 a.m. |
Created at: March 8, 2026, 3:10 p.m.