Triple
T21819728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Wijk |
E538692
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | IJhorst |
—
|
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: IJhorst | Statement: [De Wijk, locatedNear, IJhorst]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IJhorst Context triple: [De Wijk, locatedNear, IJhorst]
-
A.
IJhorst
chosen
IJhorst is a village in the Dutch province of Drenthe, known for its rural character and surrounding natural landscapes.
-
B.
Meijhorst
Meijhorst is a residential neighborhood in the Dukenburg district of Nijmegen in the Netherlands.
-
C.
Jooris
Jooris is the namesake of Stade Grimonprez-Jooris, a football stadium in Lille, France, likely honoring a notable local figure.
-
D.
De Horst
De Horst is a village in the Dutch province of Gelderland, known as part of the municipality of Berg en Dal near the city of Nijmegen.
-
E.
Joppe
Joppe is a specific area or water body within the Kagerplassen lake district in the Netherlands, known for recreational boating and watersports.
- 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cce0b8081909e20ded72db40304 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 16, 2026, 6:54 p.m.