Triple
T17264013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dender |
E419075
|
entity |
| Predicate | hasMajorTownOnBank |
P14916
|
FINISHED |
| Object | Geraardsbergen |
—
|
NE NERFINISHED |
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: Geraardsbergen | Statement: [Dender, hasMajorTownOnBank, Geraardsbergen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Geraardsbergen Context triple: [Dender, hasMajorTownOnBank, Geraardsbergen]
-
A.
Geraardsbergen
chosen
Geraardsbergen is a historic city in East Flanders, Belgium, known for its steep Muur van Geraardsbergen climb and traditional mattentaart pastries.
-
B.
Harelbeke
Harelbeke is a municipality in the Belgian province of West Flanders, known for its historic town center and as a regular host of the E3 Saxo Bank Classic cycling race.
-
C.
Izegem
Izegem is a town in the Belgian province of West Flanders, known historically for its shoe and brush industries.
-
D.
Kuurne
Kuurne is a municipality in the Belgian province of West Flanders, situated near the city of Kortrijk.
-
E.
Breskens
Breskens is a coastal town in the southwest of the Netherlands, known for its fishing harbor, North Sea beaches, and ferry connection across the Western Scheldt.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 10, 2026, 5:40 a.m.