Triple
T14774032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midden-Groningen |
E347206
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Muntendam |
E874690
|
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: Muntendam | Statement: [Midden-Groningen, hasSettlement, Muntendam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Muntendam Context triple: [Midden-Groningen, hasSettlement, Muntendam]
-
A.
Muntendam
chosen
Muntendam is a village in the Dutch province of Groningen, now administratively part of the municipality of Midden-Groningen.
-
B.
Monnickendam
Monnickendam is a historic fishing town in North Holland, Netherlands, known for its well-preserved old harbor and traditional Dutch architecture.
-
C.
Vandamm
Vandamm is a surname, often a variant spelling of "van Damm," associated with various individuals in arts, entertainment, and other fields.
-
D.
Woudenberg
Woudenberg is a small Dutch municipality and town located in the central Netherlands.
-
E.
Kropswolde
Kropswolde is a village in the Dutch province of Groningen, known for its rural character and proximity to the Zuidlaardermeer lake.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec81485e08190be35baafcf22b6f2 |
completed | April 14, 2026, 11:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0cfd26fc81909fba39c8705437ed |
completed | May 8, 2026, 4:19 p.m. |
Created at: April 10, 2026, 1:31 a.m.