Triple
T22872531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pleiku Airport |
E567235
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | PXU |
—
|
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: PXU | Statement: [Pleiku Airport, IATAcode, PXU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PXU Context triple: [Pleiku Airport, IATAcode, PXU]
-
A.
PXU
chosen
PXU is the IATA airport code for Pleiku Airport, which serves the city of Pleiku in Vietnam’s Central Highlands.
-
B.
PX
PX is a retail store on U.S. military installations that sells discounted goods and services to service members, their families, and other authorized patrons.
-
C.
PXM
PXM is the IATA airport code for Puerto Escondido International Airport, a regional airport serving the coastal city of Puerto Escondido in Oaxaca, Mexico.
-
D.
PXO
PXO is the IATA airport code for Porto Santo Airport, which serves the island of Porto Santo in Portugal’s Madeira archipelago.
-
E.
PNX
PNX is the IATA airport code for North Texas Regional Airport, a public airport serving the Sherman–Denison area in Texas, 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f55c4b88190adb49871e496ca54 |
completed | April 29, 2026, 3:47 a.m. |
Created at: April 17, 2026, 3:38 p.m.