Triple
T18085204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steenwijkerland |
E432815
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Wanneperveen |
—
|
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: Wanneperveen | Statement: [Steenwijkerland, containsSettlement, Wanneperveen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wanneperveen Context triple: [Steenwijkerland, containsSettlement, Wanneperveen]
-
A.
Wanneperveen
chosen
Wanneperveen is a rural village in the Dutch province of Overijssel, known for its lakes, peat landscapes, and water-based recreation.
-
B.
Woudenberg
Woudenberg is a small Dutch municipality and town located in the central Netherlands.
-
C.
Wassen
Wassen is a small Swiss village in the canton of Uri, known for its picturesque church and location along the Gotthard railway and road routes in the central Alps.
-
D.
Ederveen
Ederveen is a village in the Dutch province of Gelderland, known for its rural character and location within the municipality of Ede.
-
E.
Weener
Weener is a small town and municipality in the Leer district of Lower Saxony in northwestern Germany, known for its historic harbor and location on the River Ems.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4d9fdb00c8190b4769699e94c8941 |
completed | April 19, 2026, 1:34 p.m. |
Created at: April 10, 2026, 10:27 a.m.