Triple
T17107324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holten |
E415133
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Rijssen |
E413751
|
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: Rijssen | Statement: [Holten, nearbyCity, Rijssen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rijssen Context triple: [Holten, nearbyCity, Rijssen]
-
A.
Hazerswoude-Rijndijk
Hazerswoude-Rijndijk is a village in the Dutch province of South Holland, located in the municipality of Alphen aan den Rijn.
-
B.
Rijsbergen
Rijsbergen is a village in the Dutch province of North Brabant, located near the Belgian border and known for its rural character.
-
C.
Renswoude
Renswoude is a small rural municipality in the Dutch province of Utrecht, known for its historic estates and agricultural landscape.
-
D.
Rijssen-Holten
chosen
Rijssen-Holten is a municipality in the Dutch province of Overijssel, located in the Twente region and known for its mix of historic towns and nearby natural landscapes such as the Sallandse Heuvelrug.
-
E.
Driebergen-Rijsenburg
Driebergen-Rijsenburg is a village in the Dutch province of Utrecht, known for its wooded surroundings and historic estates on the Utrechtse Heuvelrug.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc280b0c8190b9e620b90e0d4b40 |
completed | April 18, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01482766508190b2af157bf039000d |
completed | May 11, 2026, 3:08 a.m. |
Created at: April 10, 2026, 5:35 a.m.