Triple
T13739603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geraardsbergen |
E330048
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object |
Nederboelare
Nederboelare is a village and sub-municipality of the city of Geraardsbergen in the Flemish region of Belgium.
|
E1057665
|
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: Nederboelare | Statement: [Geraardsbergen, contains, Nederboelare]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nederboelare Context triple: [Geraardsbergen, contains, Nederboelare]
-
A.
Niederlauer
Niederlauer is a small municipality in northern Bavaria, Germany, situated in the Franconian Saale valley and known for its rural character within the Rhön region.
-
B.
Neder-Betuwe
Neder-Betuwe is a municipality in the Dutch province of Gelderland, known for its rural landscape, fruit cultivation, and location along the rivers Waal and Rhine.
-
C.
Nederwaardse Boezem
Nederwaardse Boezem is a Dutch polder waterway and drainage basin in the province of South Holland, known for its role in regional water management near the Lek River.
-
D.
Gelderlander
Gelderlander is a regional Dutch newspaper based in the province of Gelderland.
-
E.
Boesinghe
Boesinghe is a village in West Flanders, Belgium, known for its proximity to key World War I battlefields along the Yser Front.
- 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: Nederboelare Triple: [Geraardsbergen, contains, Nederboelare]
Generated description
Nederboelare is a village and sub-municipality of the city of Geraardsbergen in the Flemish region of Belgium.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Nederboelare Target entity description: Nederboelare is a village and sub-municipality of the city of Geraardsbergen in the Flemish region of Belgium.
-
A.
Niederlauer
Niederlauer is a small municipality in northern Bavaria, Germany, situated in the Franconian Saale valley and known for its rural character within the Rhön region.
-
B.
Neder-Betuwe
Neder-Betuwe is a municipality in the Dutch province of Gelderland, known for its rural landscape, fruit cultivation, and location along the rivers Waal and Rhine.
-
C.
Nederwaardse Boezem
Nederwaardse Boezem is a Dutch polder waterway and drainage basin in the province of South Holland, known for its role in regional water management near the Lek River.
-
D.
Gelderlander
Gelderlander is a regional Dutch newspaper based in the province of Gelderland.
-
E.
Boesinghe
Boesinghe is a village in West Flanders, Belgium, known for its proximity to key World War I battlefields along the Yser Front.
- 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_69f79d6bce9881909209231f6dfcf9bf |
completed | May 3, 2026, 7:09 p.m. |
| NEDg | Description generation | batch_69f79e7869648190ab0157bd0480b219 |
completed | May 3, 2026, 7:14 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f79f7216b08190800165d46172222c |
completed | May 3, 2026, 7:18 p.m. |
Created at: April 9, 2026, 9:55 p.m.