Triple
T14186591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoeksche Waard |
E351593
|
entity |
| Predicate | hasCapital |
P204
|
FINISHED |
| Object | Maasdam |
E77635
|
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: Maasdam | Statement: [Hoeksche Waard, hasCapital, Maasdam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maasdam Context triple: [Hoeksche Waard, hasCapital, Maasdam]
-
A.
Maasdam
chosen
Maasdam is a small village in the Dutch province of South Holland, known for its rural character and association with the Maasdam cheese variety.
-
B.
Rijnmond
Rijnmond is a region in the western Netherlands centered around the port city of Rotterdam and the Rhine–Meuse river delta.
-
C.
Gooise Meren
Gooise Meren is a Dutch municipality in the province of North Holland that includes historic towns such as Naarden, Bussum, and Muiden.
-
D.
Damme
Damme is a town and municipality in the District of Vechta in Lower Saxony, Germany, known for its rural character and regional cultural traditions.
-
E.
Bergsche Maas
The Bergsche Maas is a major artificial distributary of the River Maas in the Netherlands, created in the late 19th century to improve flood control and navigation in the Dutch river delta.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61cd5778819092a03597bcdcc182 |
completed | April 14, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd19433dc08190b4d2f1aef1b2d67d |
completed | May 7, 2026, 10:59 p.m. |
Created at: April 10, 2026, 1:03 a.m.