Triple
T22219890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heusden-Zolder |
E549180
|
entity |
| Predicate | hasNeighbor |
P5707
|
FINISHED |
| Object | Beringen |
—
|
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: Beringen | Statement: [Heusden-Zolder, hasNeighbor, Beringen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beringen Context triple: [Heusden-Zolder, hasNeighbor, Beringen]
-
A.
Beringen
chosen
Beringen is a city and municipality in the Belgian province of Limburg, known for its coal mining heritage and the be-MINE industrial heritage site.
-
B.
Beringen
Beringen is a municipality in northern Switzerland known for its location near the Rhine and its surrounding vineyards and rural landscapes.
-
C.
Bergem
Bergem is a small town in southwestern Luxembourg that forms part of the commune of Mondercange.
-
D.
Bottendorf
Bottendorf is a locality in the German state of Thuringia that historically existed within the German Empire.
-
E.
Baardegem
Baardegem is a village in the Flemish province of East Flanders, Belgium, known as one of the constituent localities of the city of Aalst.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b8fa3d081908db0a0556b009d8f |
completed | April 28, 2026, 9:50 p.m. |
Created at: April 16, 2026, 8:37 p.m.