Triple
T15889859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bardufoss Airport |
E385287
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | ENDU |
E966885
|
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: ENDU | Statement: [Bardufoss Airport, ICAOcode, ENDU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ENDU Context triple: [Bardufoss Airport, ICAOcode, ENDU]
-
A.
ENDU
chosen
ENDU is the ICAO airport code for Bardufoss Airport, a regional and military airfield in Målselv, Troms, Norway.
-
B.
Endon
Endon is a village in Staffordshire, England, known as the birthplace of early 20th-century poet and critic T. E. Hulme.
-
C.
Endo
Endo is an alternative name for the Marakwet people, an ethnic community primarily residing in Kenya’s Rift Valley region.
-
D.
Nowendoc
Nowendoc is a small rural locality in the Northern Tablelands region of New South Wales, Australia, known for its rugged bushland and proximity to national parks.
-
E.
Endore
Endore is a surname most notably associated with American novelist and screenwriter Guy Endore, known for his works in horror and historical fiction.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1561d5c28819094c3541d917a4433 |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb047b6248190b6c11ef20636f50f |
completed | May 9, 2026, 10:08 p.m. |
Created at: April 10, 2026, 4:51 a.m.