Triple
T6324619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dothan Regional Airport |
E141831
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | DHN |
E583542
|
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: DHN | Statement: [Dothan Regional Airport, FAAcode, DHN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DHN Context triple: [Dothan Regional Airport, FAAcode, DHN]
-
A.
DHN
chosen
DHN is the IATA airport code for Dothan Regional Airport serving the Dothan, Alabama area in the United States.
-
B.
D.N.H.
D.N.H. is the standard legal abbreviation for the United States District Court for the District of New Hampshire, a federal trial court within the First Circuit.
-
C.
DHR
DHR is the stock ticker symbol for Danaher Corporation, a global science and technology company focused on life sciences, diagnostics, and environmental and applied solutions.
-
D.
DH
DH is the postcode area covering Durham and surrounding parts of North East England in the United Kingdom.
-
E.
DH
DH is the commonly used currency symbol representing the Moroccan dirham.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e538ac81908c5d7556513c2bc3 |
completed | March 22, 2026, 9:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6040b1e0481908095decce40107b4 |
completed | March 27, 2026, 4:14 a.m. |
Created at: March 22, 2026, 4:29 p.m.