Triple
T18931203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weert |
E463111
|
entity |
| Predicate | hasNeighbouringMunicipality |
P224
|
FINISHED |
| Object | Maasgouw |
E1345631
|
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: Maasgouw | Statement: [Weert, hasNeighbouringMunicipality, Maasgouw]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maasgouw Context triple: [Weert, hasNeighbouringMunicipality, Maasgouw]
-
A.
Maasgouw
chosen
Maasgouw is a municipality in the Dutch province of Limburg, known for its historic villages and location along the river Maas.
-
B.
Maasmechelen
Maasmechelen is a municipality in the Belgian province of Limburg, known for its proximity to the Meuse River and the popular Maasmechelen Village outlet shopping center.
-
C.
Maasmond
Maasmond is the Dutch name for the estuary where the River Meuse (Maas) flows into the North Sea, an important maritime gateway in the Netherlands.
-
D.
Maasbracht
Maasbracht is a town in the Dutch province of Limburg, known as an inland port and industrial center along the River Meuse.
-
E.
Zandbergen
Zandbergen is a village in East Flanders, Belgium, that forms part of the municipality of Geraardsbergen.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9c0b84881909ad6da9522203df8 |
completed | April 20, 2026, 6:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a05912043c48190813e3dc5e432b68e |
completed | May 14, 2026, 9:08 a.m. |
Created at: April 10, 2026, 11:59 a.m.