Triple
T13704223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eemnes |
E328597
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Eemnes-Binnen |
E328597
|
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: Eemnes-Binnen | Statement: [Eemnes, hasSettlement, Eemnes-Binnen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eemnes-Binnen Context triple: [Eemnes, hasSettlement, Eemnes-Binnen]
-
A.
Eemnes
chosen
Eemnes is a small town and municipality in the central Netherlands known for its characteristic polder landscape and historic village centers.
-
B.
Raalte
Raalte is a town and municipality in the Dutch province of Overijssel, known for its agricultural surroundings and regional festivals.
-
C.
Volkmarsen
Volkmarsen is a small town in the Waldeck-Frankenberg district of northern Hesse, Germany, known for its historic town center and rural surroundings.
-
D.
Eemster
Eemster is a small village in the Dutch province of Drenthe, situated within the municipality of Westerveld.
-
E.
Oombergen
Oombergen is a village and former municipality in East Flanders, Belgium, now incorporated into the city of Zottegem.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad162158819089280ee1e6b5c2cf |
completed | April 13, 2026, 8:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f79d50f34c8190ac5b4e09ab57baa9 |
completed | May 3, 2026, 7:09 p.m. |
Created at: April 9, 2026, 9:54 p.m.