Triple
T22155228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N35 road |
E547517
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Holten |
—
|
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: Holten | Statement: [N35 road, passesNear, Holten]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holten Context triple: [N35 road, passesNear, Holten]
-
A.
Holten
chosen
Holten is a village in the Dutch province of Overijssel known as a gateway to the Sallandse Heuvelrug National Park and its surrounding natural landscapes.
-
B.
Vaals
Vaals is a Dutch town in the province of Limburg, known for its location at the tripoint where the Netherlands, Germany, and Belgium meet.
-
C.
Rolandswerth
Rolandswerth is a district of the German town of Remagen, situated along the Rhine River in the state of Rhineland-Palatinate.
-
D.
Hilden
Hilden is a small rural community located in Colchester County in the Canadian province of Nova Scotia.
-
E.
Hilden
Hilden is a town in western Germany’s North Rhine-Westphalia region, known for its proximity to Düsseldorf and its mix of residential, commercial, and light industrial areas.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f7d034819092ecf9682e549c9a |
completed | April 28, 2026, 9:43 p.m. |
Created at: April 16, 2026, 8:33 p.m.