Triple
T21784873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ham |
E537808
|
entity |
| Predicate | hasNeighbouringMunicipality |
P224
|
FINISHED |
| Object | Tessenderlo |
—
|
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: Tessenderlo | Statement: [Ham, hasNeighbouringMunicipality, Tessenderlo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tessenderlo Context triple: [Ham, hasNeighbouringMunicipality, Tessenderlo]
-
A.
Tessenderlo
chosen
Tessenderlo is a municipality in the Belgian province of Limburg, known for its chemical industry and location near the Albert Canal.
-
B.
Roeselare
Roeselare is a city in western Belgium known as an economic and commercial center in the province of West Flanders.
-
C.
Izegem
Izegem is a town in the Belgian province of West Flanders, known historically for its shoe and brush industries.
-
D.
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.
-
E.
Erembodegem
Erembodegem is a village in the Belgian province of East Flanders that forms part 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_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.