Triple
T22657316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Kempen |
E559261
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Grobbendonk |
—
|
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: Grobbendonk | Statement: [De Kempen, hasSettlement, Grobbendonk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grobbendonk Context triple: [De Kempen, hasSettlement, Grobbendonk]
-
A.
Grobbendonk
chosen
Grobbendonk is a municipality in the Belgian province of Antwerp, known as the birthplace of legendary cyclist Rik Van Looy.
-
B.
Bottendorf
Bottendorf is a locality in the German state of Thuringia that historically existed within the German Empire.
-
C.
Merode
Merode is a key Brussels Metro station serving as an important interchange point near the Parc du Cinquantenaire in eastern Brussels.
-
D.
Kanegem
Kanegem is a small village in West Flanders, Belgium, known for its historic church and rural character.
-
E.
Leubringhen
Leubringhen is a small commune in northern France, situated in the Pas-de-Calais department near the English Channel coast.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765c62bc8190b3fcde76d6b6dfb6 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 3:06 p.m.