Triple
T15346161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoeksche Waard |
E366923
|
entity |
| Predicate | mergerOfFormerMunicipality |
P5557
|
FINISHED |
| Object | Cromstrijen |
E788554
|
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: Cromstrijen | Statement: [Hoeksche Waard, mergerOfFormerMunicipality, Cromstrijen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cromstrijen Context triple: [Hoeksche Waard, mergerOfFormerMunicipality, Cromstrijen]
-
A.
Cromstrijen
chosen
Cromstrijen was a former municipality in the Dutch province of South Holland, comprising several villages on the island of Hoeksche Waard.
-
B.
Kromme Mijdrecht
Kromme Mijdrecht is a small river in the Netherlands that serves as one of the headwaters of the Amstel.
-
C.
Woudenberg
Woudenberg is a small Dutch municipality and town located in the central Netherlands.
-
D.
Kropswolde
Kropswolde is a village in the Dutch province of Groningen, known for its rural character and proximity to the Zuidlaardermeer lake.
-
E.
Zandkreek
Zandkreek is a tidal waterway and former estuary in the Dutch province of Zeeland, known for its role in regional water management and coastal protection.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e1749bc8190a8b9cbcb27288a5b |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff1a67adf88190bbe15040761d235e |
completed | May 9, 2026, 11:28 a.m. |
Created at: April 10, 2026, 3:17 a.m.