Triple
T19714438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triangle North Executive Airport |
E473435
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | LHZ |
—
|
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: LHZ | Statement: [Triangle North Executive Airport, FAA LID, LHZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LHZ Context triple: [Triangle North Executive Airport, FAA LID, LHZ]
-
A.
LHZ
chosen
LHZ is the IATA airport code for Triangle North Executive Airport, a public airport serving the Louisburg, North Carolina area.
-
B.
LHX
LHX is the stock ticker symbol for L3Harris Technologies, a major American defense and aerospace technology company.
-
C.
HLZ
HLZ is the IATA airport code for Hamilton Airport in New Zealand, serving the city of Hamilton and the surrounding Waikato region.
-
D.
LZ
LZ is the stock ticker symbol for The Lubrizol Corporation, a specialty chemicals company known for its lubricant additives and advanced materials.
-
E.
LZ
LZ is the vehicle registration code assigned to the municipality of Kals am Großglockner in Austria.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6440b47508190a8a33325b00841dc |
completed | April 20, 2026, 3:19 p.m. |
Created at: April 10, 2026, 1:46 p.m.