Triple
T21034143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Junta Municipal Airport |
E518143
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | LHX |
—
|
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: LHX | Statement: [La Junta Municipal Airport, IATA code, LHX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LHX Context triple: [La Junta Municipal Airport, IATA code, LHX]
-
A.
LHX
chosen
LHX is the stock ticker symbol for L3Harris Technologies, a major American defense and aerospace technology company.
-
B.
LHZ
LHZ is the IATA airport code for Triangle North Executive Airport, a public airport serving the Louisburg, North Carolina area.
-
C.
HLX
HLX is the ICAO airline designator for Hapag-Lloyd Express, a former German low-cost carrier.
-
D.
LTX
LTX is the IATA airport code for Cotopaxi International Airport serving Latacunga, Ecuador.
-
E.
LX
LX is the second-generation Holden Torana series produced in the mid-1970s, notable for introducing the A9X performance package and being a popular Australian mid-size car in both road and racing forms.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc84b4ac8190bcee5fbba730b499 |
completed | April 21, 2026, 4:26 a.m. |
Created at: April 16, 2026, 2:01 p.m.