Triple
T16929946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Groningen Airport Eelde |
E410678
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Eelde |
—
|
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: Eelde | Statement: [Groningen Airport Eelde, locatedIn, Eelde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eelde Context triple: [Groningen Airport Eelde, locatedIn, Eelde]
-
A.
Eelde
chosen
Eelde is a village in the Dutch province of Drenthe, known for its proximity to Groningen Airport Eelde and its historic annual flower parade.
-
B.
Gogeldrie
Gogeldrie is a small rural locality in the Riverina region of New South Wales, Australia, known for its agricultural surroundings and proximity to the Murrumbidgee River.
-
C.
Oudelande
Oudelande is a small village in the Dutch province of Zeeland, known for its rural character and traditional polder landscape.
-
D.
Veenendaal
Veenendaal is a Dutch town and municipality in the central Netherlands, known for its location between Utrecht and the Veluwe and its mix of residential, commercial, and light industrial areas.
-
E.
Elingaard
Elingaard is a historic estate and former manor located in the municipality of Rygge in southeastern Norway.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf248c6c81908fbf4d49e5381f08 |
completed | April 18, 2026, 6:36 p.m. |
Created at: April 10, 2026, 5:30 a.m.