Triple
T23006092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Moerdijk |
E572772
|
entity |
| Predicate | hasAdministrativeCenter |
P1474
|
FINISHED |
| Object | Zevenbergen |
—
|
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: Zevenbergen | Statement: [municipality of Moerdijk, hasAdministrativeCenter, Zevenbergen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zevenbergen Context triple: [municipality of Moerdijk, hasAdministrativeCenter, Zevenbergen]
-
A.
Zevenbergen
chosen
Zevenbergen is a town in the Dutch province of North Brabant, known historically for its peat extraction and as part of the municipality of Moerdijk.
-
B.
Zandbergen
Zandbergen is a village in East Flanders, Belgium, that forms part of the municipality of Geraardsbergen.
-
C.
Zandbergen
Zandbergen is a small hamlet in the municipality of Losser in the province of Overijssel in the eastern Netherlands.
-
D.
Zevenaarsehoek
Zevenaarsehoek is a small settlement in the Dutch municipality of Montferland in the province of Gelderland.
-
E.
Steenbergen
Steenbergen is a small village located in the municipality of Noordenveld in the Dutch province of Drenthe.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1835706dc8190b3f9743c0f336bb2 |
completed | April 29, 2026, 4:04 a.m. |
Created at: April 17, 2026, 3:51 p.m.