Triple
T15812543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flemish Ardennes |
E383389
|
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: [Flemish Ardennes, contains, Horebeke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horebeke Context triple: [Flemish Ardennes, contains, Horebeke]
-
A.
Horebeke
chosen
Horebeke is a small rural municipality in the Flemish Ardennes region of East Flanders, Belgium.
-
B.
Wachtebeke
Wachtebeke is a municipality in the East Flanders province of Belgium, known for its rural character and natural areas such as the Puyenbroeck provincial domain.
-
C.
Holsbeek
Holsbeek is a municipality in the Flemish Brabant province of Belgium, known for its rural character and historic Horst Castle.
-
D.
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.
-
E.
Wielsbeke
Wielsbeke is a municipality in the Belgian province of West Flanders.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a069bc8190bf9504dc6c998fa2 |
completed | April 16, 2026, 11:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb5997a988190b7965e42d283459a |
completed | May 9, 2026, 10:30 p.m. |
Created at: April 10, 2026, 4:49 a.m.