Triple
T4855029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duluth International Airport |
E108515
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | DLH |
E475034
|
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: DLH | Statement: [Duluth International Airport, FAAcode, DLH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DLH Context triple: [Duluth International Airport, FAAcode, DLH]
-
A.
DLH
DLH is the ICAO airline designator used for Lufthansa, Germany's largest and flag carrier airline.
-
B.
DLH
chosen
DLH is the IATA airport code for Duluth International Airport, a commercial and general aviation airport serving Duluth, Minnesota, and the surrounding region.
-
C.
KDLH
KDLH is the ICAO airport code for Duluth International Airport, a public airport serving Duluth, Minnesota, and the surrounding region.
-
D.
Dellner
Dellner is a company specializing in railway coupling and connection systems used on modern passenger and freight trains worldwide.
-
E.
DLG
DLG is the vehicle registration code for the municipality of Blindheim in Germany.
- 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d3c9d7881908c04cef2cb7db745 |
completed | March 20, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be67da14d48190a994a11eb7a674b5 |
completed | March 21, 2026, 9:41 a.m. |
Created at: March 20, 2026, 1:26 p.m.