Triple
T21183356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roosendaal |
E522007
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Woensdrecht |
—
|
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: Woensdrecht | Statement: [Roosendaal, borderedBy, Woensdrecht]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Woensdrecht Context triple: [Roosendaal, borderedBy, Woensdrecht]
-
A.
Woensdrecht
chosen
Woensdrecht is a municipality in the Dutch province of North Brabant, known for its strategic location near the Belgian border and its military air base.
-
B.
Zwijndrecht
Zwijndrecht is a Dutch town and municipality located in the western Netherlands, known for its position along the rivers near the city of Dordrecht.
-
C.
Woudwetering
Woudwetering is a Dutch waterway in South Holland that serves as an important local canal near the village of Woubrugge.
-
D.
Oranjewoud
Oranjewoud is a historic estate and village in the Dutch province of Friesland, long associated with the royal House of Orange-Nassau.
-
E.
Maasbracht
Maasbracht is a town in the Dutch province of Limburg, known as an inland port and industrial center along the River Meuse.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301f7f1c81908686866fdee57127 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 3:05 p.m.