Triple
T20766601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veldhoven |
E511113
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Waalre |
—
|
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: Waalre | Statement: [Veldhoven, borderedBy, Waalre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Waalre Context triple: [Veldhoven, borderedBy, Waalre]
-
A.
Waalre
chosen
Waalre is a municipality and village in the southern Netherlands, located in the province of North Brabant near the city of Eindhoven.
-
B.
Bierbeek
Bierbeek is a municipality in the Flemish Brabant province of Belgium, located near the city of Leuven.
-
C.
Overijse
Overijse is a municipality in the Flemish Brabant province of Belgium, known for its green residential character and extensive vineyards.
-
D.
Maasbracht
Maasbracht is a town in the Dutch province of Limburg, known as an inland port and industrial center along the River Meuse.
-
E.
Oudenarde
Oudenarde (Oudenaarde) is a historic town in East Flanders, Belgium, known for its medieval architecture, tapestry production, and role in early modern European conflicts.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24ceab8819094e331c57abe6879 |
completed | April 21, 2026, 12:18 a.m. |
Created at: April 16, 2026, 12:36 p.m.