Triple
T22615831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Heusden |
E558142
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Doeveren |
—
|
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: Doeveren | Statement: [municipality of Heusden, contains, Doeveren]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Doeveren Context triple: [municipality of Heusden, contains, Doeveren]
-
A.
Doeveren
chosen
Doeveren is a small village in the Dutch province of North Brabant, situated within the historical region known as the Land van Heusden.
-
B.
Tovere
Tovere is a small locality or hamlet that forms part of the municipality of Moltrasio in northern Italy’s Lake Como area.
-
C.
Diever
Diever is a village in the Dutch province of Drenthe, known for its historic center and open-air Shakespeare theatre.
-
D.
Odoornerveen
Odoornerveen is a village in the Dutch province of Drenthe, known for its rural character and location within the municipality of Borger-Odoorn.
-
E.
Everschop
Everschop was a former historical region or administrative unit that later became part of the Eiderstedt peninsula in northern Germany.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f167edec2481909c2f06607b3cb8f6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 2:59 p.m.