Triple
T18437406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lierde |
E450428
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Zottegem |
E326228
|
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: Zottegem | Statement: [Lierde, locatedNear, Zottegem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zottegem Context triple: [Lierde, locatedNear, Zottegem]
-
A.
Zottegem
chosen
Zottegem is a city and municipality in East Flanders, Belgium, known for its historic center and its role as a regular feature in Flemish cycling races.
-
B.
Izegem
Izegem is a town in the Belgian province of West Flanders, known historically for its shoe and brush industries.
-
C.
Edegem
Edegem is a municipality in the Belgian province of Antwerp, known as a residential suburb south of the city of Antwerp.
-
D.
Wommelgem
Wommelgem is a municipality in the Belgian province of Antwerp, known for its suburban character and proximity to the city of Antwerp.
-
E.
Aalst
Aalst is a historic city in the Belgian province of East Flanders, known for its textile industry and famous annual carnival.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c0e04508190bc851a8954ae60e8 |
completed | April 19, 2026, 6:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a04915d574081909e2a8fd9be0e1643 |
completed | May 13, 2026, 2:57 p.m. |
Created at: April 10, 2026, 11:29 a.m.