Triple
T15131082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ovezande |
E361419
|
entity |
| Predicate | hasRoadConnectionTo |
P11435
|
FINISHED |
| Object | Driewegen |
E361421
|
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: Driewegen | Statement: [Ovezande, hasRoadConnectionTo, Driewegen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Driewegen Context triple: [Ovezande, hasRoadConnectionTo, Driewegen]
-
A.
Driewegen
chosen
Driewegen is a small village in the Dutch province of Zeeland, located within the municipality of Borsele.
-
B.
Heenweg
Heenweg is a small village in the Dutch municipality of Westland in the province of South Holland, Netherlands.
-
C.
Den Dreef
Den Dreef is a football stadium in Leuven, Belgium, best known as the home ground of Oud-Heverlee Leuven.
-
D.
Land van Rijen
Land van Rijen is a historical region within Belgium’s Antwerp Province, known for its rural landscapes and traditional Flemish character.
-
E.
Oversticht
Oversticht was a medieval territorial region in the northern Low Countries that roughly corresponds to much of the modern Dutch province of Overijssel and surrounding areas.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b194748190801e3956bf2429d4 |
completed | April 15, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feb7fa449c8190aed8941168b063c3 |
completed | May 9, 2026, 4:28 a.m. |
Created at: April 10, 2026, 3:06 a.m.