Triple
T8641438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrondissement of Oudenaarde |
E204657
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Horebeke |
E233028
|
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: Horebeke | Statement: [Arrondissement of Oudenaarde, contains, Horebeke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horebeke Context triple: [Arrondissement of Oudenaarde, contains, Horebeke]
-
A.
Horebeke
chosen
Horebeke is a small rural municipality in the Flemish Ardennes region of East Flanders, Belgium.
-
B.
Meerbeke
Meerbeke is a village in East Flanders, Belgium, best known for having long served as the traditional finish town of the Tour of Flanders cycling race.
-
C.
Moortebeek
Moortebeek is a residential district within the Brussels municipality of Anderlecht in Belgium.
-
D.
Lembeek
Lembeek is a village in the Belgian municipality of Halle, located along the Senne River in the province of Flemish Brabant.
-
E.
Michelbeke
Michelbeke is a village in the municipality of Brakel in East Flanders, Belgium, known for its rural character and cycling-friendly landscape.
- 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_69ca834ca1c88190a11ffb0200342fac |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4795b07081908bfc9ebf35a50f07 |
completed | March 31, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d065b11f3c81909c787d365b242d57 |
completed | April 4, 2026, 1:13 a.m. |
Created at: March 30, 2026, 6:28 p.m.