Triple
T13739606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geraardsbergen |
E330048
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object |
Smeerebbe-Vloerzegem
Smeerebbe-Vloerzegem is a village in the Flemish province of East Flanders, Belgium, forming part of the municipality of Geraardsbergen.
|
E1098589
|
NE FINISHED |
How this triple was built (4 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: Smeerebbe-Vloerzegem | Statement: [Geraardsbergen, contains, Smeerebbe-Vloerzegem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Smeerebbe-Vloerzegem Context triple: [Geraardsbergen, contains, Smeerebbe-Vloerzegem]
-
A.
Baambrugge
Baambrugge is a small village in the Dutch province of Utrecht, known for its rural character and location along the river Angstel.
-
B.
Steenokkerzeel
Steenokkerzeel is a municipality in the Belgian province of Flemish Brabant, known for its proximity to Brussels and its location near major transport infrastructure.
-
C.
Velzeke
Velzeke is a village in East Flanders, Belgium, known for its archaeological heritage and status as a sub-municipality of Zottegem.
-
D.
Kanegem
Kanegem is a small village in West Flanders, Belgium, known for its historic church and rural character.
-
E.
Lembeek
Lembeek is a village in the Belgian municipality of Halle, located along the Senne River in the province of Flemish Brabant.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Smeerebbe-Vloerzegem Triple: [Geraardsbergen, contains, Smeerebbe-Vloerzegem]
Generated description
Smeerebbe-Vloerzegem is a village in the Flemish province of East Flanders, Belgium, forming part of the municipality of Geraardsbergen.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Smeerebbe-Vloerzegem Target entity description: Smeerebbe-Vloerzegem is a village in the Flemish province of East Flanders, Belgium, forming part of the municipality of Geraardsbergen.
-
A.
Baambrugge
Baambrugge is a small village in the Dutch province of Utrecht, known for its rural character and location along the river Angstel.
-
B.
Steenokkerzeel
Steenokkerzeel is a municipality in the Belgian province of Flemish Brabant, known for its proximity to Brussels and its location near major transport infrastructure.
-
C.
Velzeke
Velzeke is a village in East Flanders, Belgium, known for its archaeological heritage and status as a sub-municipality of Zottegem.
-
D.
Kanegem
Kanegem is a small village in West Flanders, Belgium, known for its historic church and rural character.
-
E.
Lembeek
Lembeek is a village in the Belgian municipality of Halle, located along the Senne River in the province of Flemish Brabant.
- F. None of above. chosen
Provenance (5 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de0204d50c8190a5413cc9a1b26e14 |
completed | April 14, 2026, 8:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bb05bb481909a0ad528e998fdf1 |
completed | May 8, 2026, 3:42 a.m. |
| NEDg | Description generation | batch_69fd5d078b8081908810acb77be74b2b |
completed | May 8, 2026, 3:48 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69fd5d7e07a08190be5154674f7478fb |
completed | May 8, 2026, 3:50 a.m. |
Created at: April 9, 2026, 9:55 p.m.