Triple
T5030570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land van Cuijk |
E113289
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Wijchen |
E303012
|
NE FINISHED |
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: Wijchen | Statement: [Land van Cuijk, hasBorderWith, Wijchen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wijchen Context triple: [Land van Cuijk, hasBorderWith, Wijchen]
-
A.
Wijchen
chosen
Wijchen is a town and municipality in the Dutch province of Gelderland, located just southwest of the city of Nijmegen.
-
B.
Gorinchem
Gorinchem is a historic fortified city in the Netherlands known for its well-preserved city walls and picturesque old town.
-
C.
Roermond
Roermond is a historic city in the southeastern Netherlands known for its medieval architecture, prominent churches, and large designer outlet shopping center.
-
D.
Harderwijk
Harderwijk is a historic Dutch city known for its former Hanseatic trading role and scenic location on the shores of the Veluwemeer.
-
E.
Nijmegen
Nijmegen is a historic Dutch city near the German border that played a crucial strategic role during World War II, particularly in the Allied advance in 1944.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73922a4c81908651c2d9b5e01cb6 |
completed | March 20, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4f31e3d5c8190a044eaf67ebc9f08 |
completed | April 19, 2026, 3:22 p.m. |
Created at: March 20, 2026, 1:36 p.m.