Triple
T22153993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronckhorst |
E547485
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Steenderen |
—
|
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: Steenderen | Statement: [Bronckhorst, containsSettlement, Steenderen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Steenderen Context triple: [Bronckhorst, containsSettlement, Steenderen]
-
A.
Steenderen
chosen
Steenderen is a village and former municipality in the province of Gelderland in the Netherlands, now part of the municipality of Bronckhorst.
-
B.
Steenbergen
Steenbergen is a municipality and town in the Dutch province of North Brabant, known for its rural landscape and proximity to several major waterways.
-
C.
Steenbergen
Steenbergen is a small village located in the municipality of Noordenveld in the Dutch province of Drenthe.
-
D.
Kesteren
Kesteren is a village in the Dutch province of Gelderland, situated along the Nederrijn river in the central Netherlands.
-
E.
Heemstede
Heemstede is a town and municipality in the province of North Holland in the Netherlands, known as a leafy residential suburb near Haarlem.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f6d5b88190badee2e515a3b633 |
completed | April 28, 2026, 9:43 p.m. |
Created at: April 16, 2026, 8:33 p.m.