Triple
T5893216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oss |
E131039
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Uden |
E131040
|
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: Uden | Statement: [Oss, borderedBy, Uden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uden Context triple: [Oss, borderedBy, Uden]
-
A.
Uden
chosen
Uden is a town in the southern Netherlands known for its location in the province of North Brabant and its proximity to nature reserves and regional industry.
-
B.
Unna
Unna is a town in the German state of North Rhine-Westphalia, known historically as a regional trading center near Dortmund.
-
C.
Undy
Undy is a village in Monmouthshire, Wales, situated near the town of Caldicot in the southeast of the country.
-
D.
Vanløse
Vanløse is a residential district in the western part of Copenhagen, Denmark, known for its local shopping streets, green areas, and strong public transport connections.
-
E.
Uddel
Uddel is a village in the Dutch province of Gelderland, situated on the Veluwe and known for its rural character and surrounding forests and heathlands.
- 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_69c0b15146888190ab86eaf9e565ee28 |
completed | March 23, 2026, 3:19 a.m. |
Created at: March 22, 2026, 3:58 p.m.