Triple
T23133822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olst-Wijhe |
E577253
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Voorst |
—
|
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: Voorst | Statement: [Olst-Wijhe, borderedBy, Voorst]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Voorst Context triple: [Olst-Wijhe, borderedBy, Voorst]
-
A.
Voorst
chosen
Voorst is a municipality and village in the province of Gelderland in the eastern Netherlands, known for its rural character and historic estates.
-
B.
Wiekevorst
Wiekevorst is a village in the Belgian province of Antwerp that forms part of the municipality of Heist-op-den-Berg.
-
C.
Voorde
Voorde is a village in the Flemish province of East Flanders, Belgium, that forms one of the municipal districts of the city of Ninove.
-
D.
Boesinghe
Boesinghe is a village in West Flanders, Belgium, known for its proximity to key World War I battlefields along the Yser Front.
-
E.
Lodewijck
Lodewijck is a Dutch given name, an older or variant spelling of Lodewijk, equivalent to the English name Louis.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e89cce881908727a94dbc00e031 |
completed | April 29, 2026, 4:52 a.m. |
Created at: April 17, 2026, 4 p.m.