Triple
T20709365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrondissement of Charleroi |
E508991
|
entity |
| Predicate | containsMunicipality |
P852
|
FINISHED |
| Object | Gerpinnes |
—
|
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: Gerpinnes | Statement: [Arrondissement of Charleroi, containsMunicipality, Gerpinnes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gerpinnes Context triple: [Arrondissement of Charleroi, containsMunicipality, Gerpinnes]
-
A.
Gerpinnes
chosen
Gerpinnes is a municipality in the Walloon region of Belgium, known for its rural character and traditional Saint-Roch procession.
-
B.
Gottignies
Gottignies is a village in the municipality of Le Roeulx in the province of Hainaut, Belgium.
-
C.
Erquelinnes
Erquelinnes is a municipality in the province of Hainaut in Wallonia, Belgium, located near the French border along the Sambre River.
-
D.
Sterpigny
Sterpigny is a small village in the municipality of Gouvy in the province of Luxembourg, Belgium.
-
E.
Pétange
Pétange is a commune in southwestern Luxembourg known for its proximity to the borders with Belgium and France and its role as a local transport and industrial hub.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1961090819090daf7254f90a176 |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 12:14 p.m.