Triple
T5893250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uden |
E131040
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Veghel |
E177331
|
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: Veghel | Statement: [Uden, near, Veghel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Veghel Context triple: [Uden, near, Veghel]
-
A.
Veghel
chosen
Veghel is a town in the southern Netherlands known as an industrial and logistics hub within the province of North Brabant.
-
B.
Yerseke
Yerseke is a Dutch village in the province of Zeeland, best known for its mussel and oyster farming along the Eastern Scheldt.
-
C.
Zundert
Zundert is a municipality and town in the southern Netherlands, known as the birthplace of painter Vincent van Gogh and for hosting one of the world's largest flower parades.
-
D.
Veldhoven
Veldhoven is a town and municipality in the southern Netherlands, located near Eindhoven in the province of North Brabant.
-
E.
Coevorden
Coevorden is a historic city and municipality in the northeastern Netherlands, known for its medieval fortress layout and strategic location near the German border.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c036b5c68481909fdcba428238c74d |
completed | March 22, 2026, 6:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6eec098348190a01ca8eca035592c |
completed | March 27, 2026, 8:55 p.m. |
Created at: March 22, 2026, 3:58 p.m.