Triple
T21542544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koekange |
E531527
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | De Wijk |
—
|
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: De Wijk | Statement: [Koekange, locatedNear, De Wijk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: De Wijk Context triple: [Koekange, locatedNear, De Wijk]
-
A.
De Wijk
chosen
De Wijk is a village in the Dutch province of Drenthe, known for its historic buildings and rural character within the municipality of De Wolden.
-
B.
Wijk
Wijk is a short form of the Dutch given name Lodewijk, commonly used as an informal or familiar variant.
-
C.
Maatschappijwijk
Maatschappijwijk is a small settlement located within the municipality of Utrechtse Heuvelrug in the Dutch province of Utrecht.
-
D.
Bullewijk
Bullewijk is a small waterway and urban canal in Amsterdam’s southeastern area, integrated into the city’s network of rivers and canals.
-
E.
Westwijk
Westwijk is a residential district in Amstelveen, Netherlands, served as the southern terminus of Amsterdam’s former metro line 51.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb58c34808190b0eb54ba01e2cc13 |
completed | April 27, 2026, 1:02 a.m. |
Created at: April 16, 2026, 6:28 p.m.