Triple
T3068642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Dhabi International Airport |
E62165
|
entity |
| Predicate | hasAirportCode |
P6089
|
FINISHED |
| Object | OMAA |
E322130
|
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: OMAA | Statement: [Abu Dhabi International Airport, hasAirportCode, OMAA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OMAA Context triple: [Abu Dhabi International Airport, hasAirportCode, OMAA]
-
A.
OMAA
chosen
OMAA is the ICAO airport code designating Abu Dhabi International Airport, the main international gateway to Abu Dhabi in the United Arab Emirates.
-
B.
OMA
OMA is a renowned international architecture firm known for its innovative, often experimental designs and influential contributions to contemporary architecture.
-
C.
OMA
OMA is the ICAO airline designator assigned to Oman Air, the national carrier of Oman.
-
D.
OMA
OMA is the IATA airport code for Eppley Airfield, the primary commercial airport serving Omaha, Nebraska.
-
E.
OM
OM is an American experimental rock band known for its hypnotic, drone-influenced sound and spiritually themed compositions.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada0ffcc208190962cc9edcbf43c31 |
completed | March 8, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1f87bec6c8190ae928fc7c4467859 |
completed | March 11, 2026, 11:19 p.m. |
Created at: March 8, 2026, 3:02 p.m.