Triple
T7709709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grayson County Airport |
E174716
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | PNX |
E165601
|
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: PNX | Statement: [Grayson County Airport, IATAcode, PNX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PNX Context triple: [Grayson County Airport, IATAcode, PNX]
-
A.
PNX
chosen
PNX is the IATA airport code for North Texas Regional Airport, a public airport serving the Sherman–Denison area in Texas, United States.
-
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.
PN
PN is the vehicle registration code used for the Italian city and province of Pordenone in the Friuli Venezia Giulia region.
-
D.
PN
PN is the official abbreviation for the Philippine Navy, the naval warfare branch of the Armed Forces of the Philippines.
-
E.
PKX
PKX is the IATA airport code for Beijing Daxing International Airport, a major international aviation hub serving Beijing, China.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ac0060819084f9c0242a5ffa9a |
completed | March 27, 2026, 10:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8accc07f4819089a07726c8313839 |
completed | March 29, 2026, 4:38 a.m. |
Created at: March 27, 2026, 4:04 p.m.