Triple
T21785274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voeren |
E537818
|
entity |
| Predicate | hasOfficialName |
P66
|
FINISHED |
| Object | Voeren |
—
|
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: Voeren | Statement: [Voeren, hasOfficialName, Voeren]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Voeren Context triple: [Voeren, hasOfficialName, Voeren]
-
A.
Voeren
chosen
Voeren is a small, Dutch-speaking municipality in the easternmost part of Belgium, known for its rural landscape and linguistic and cultural border position between Flanders, Wallonia, and the Netherlands.
-
B.
Brouwershaven
Brouwershaven is a small historic town in the Dutch province of Zeeland, known for its maritime heritage and well-preserved old center.
-
C.
Terneuzen
Terneuzen is a port city and municipality in the southwestern Netherlands, known for its location on the Western Scheldt and its role in shipping access to the port of Ghent.
-
D.
Heessen
Heessen is a district of the German city of Hamm, located in the state of North Rhine-Westphalia.
-
E.
Volendam
Volendam is a traditional Dutch fishing village and popular tourist destination known for its historic harbor, wooden houses, and preserved local costumes.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f04630f4f08190910b9e499a4249ca |
completed | April 28, 2026, 5:31 a.m. |
Created at: April 16, 2026, 6:52 p.m.