Triple
T22340100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Graeff family |
E552248
|
entity |
| Predicate | estate |
P14553
|
FINISHED |
| Object | Zuid-Polsbroek |
—
|
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: Zuid-Polsbroek | Statement: [De Graeff family, estate, Zuid-Polsbroek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zuid-Polsbroek Context triple: [De Graeff family, estate, Zuid-Polsbroek]
-
A.
Polsbroek
chosen
Polsbroek is a small village in the Dutch province of Utrecht, known for its rural character and location along the river Vlist.
-
B.
Zuidbroek
Zuidbroek is a village in the province of Groningen in the northeastern Netherlands, known historically as a small canal-side settlement in a largely rural landscape.
-
C.
Velserbroek
Velserbroek is a village in North Holland, Netherlands, situated near the historic Beeckestijn estate and forming part of the municipality of Velsen.
-
D.
Willebroek
Willebroek is a municipality in northern Belgium known for its canal connections and location between Brussels and Antwerp.
-
E.
Bennebroek
Bennebroek is a small town in North Holland, Netherlands, known as one of the country’s smallest former municipalities before merging into Bloemendaal.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157824f588190882bea9e61dd5a83 |
completed | April 29, 2026, 12:57 a.m. |
Created at: April 16, 2026, 8:43 p.m.