Triple
T17264066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denderstreek |
E419077
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Lebbeke |
E1041484
|
NE FINISHED |
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: Lebbeke | Statement: [Denderstreek, hasPart, Lebbeke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lebbeke Context triple: [Denderstreek, hasPart, Lebbeke]
-
A.
Lebbeke
chosen
Lebbeke is a municipality in the Belgian province of East Flanders, known as the birthplace of former football goalkeeper Jean-Marie Pfaff.
-
B.
Laarbeek
Laarbeek is a municipality in the southern Netherlands, in the province of North Brabant, comprising several villages including Beek en Donk, Lieshout, and Aarle-Rixtel.
-
C.
Michelbeke
Michelbeke is a village in the municipality of Brakel in East Flanders, Belgium, known for its rural character and cycling-friendly landscape.
-
D.
Tombeek
Tombeek is a village and sub-municipality of Overijse in the Flemish Brabant province of Belgium.
-
E.
Horebeke
Horebeke is a small rural municipality in the Flemish Ardennes region of East Flanders, Belgium.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4432fc81908fd90865822af1fa |
completed | April 19, 2026, 1:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0171054f388190bf068ca2e6b88458 |
completed | May 11, 2026, 6:02 a.m. |
Created at: April 10, 2026, 5:40 a.m.