Triple
T13869322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deinze |
E333407
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | Petegem-aan-de-Leie |
E100113
|
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: Petegem-aan-de-Leie | Statement: [Deinze, hasSubdivision, Petegem-aan-de-Leie]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petegem-aan-de-Leie Context triple: [Deinze, hasSubdivision, Petegem-aan-de-Leie]
-
A.
Zonnebeke
Zonnebeke is a municipality in West Flanders, Belgium, known for its significant World War I battlefields and memorials.
-
B.
Kanegem
Kanegem is a small village in West Flanders, Belgium, known for its historic church and rural character.
-
C.
Izegem
Izegem is a town in the Belgian province of West Flanders, known historically for its shoe and brush industries.
-
D.
Oudenarde
chosen
Oudenarde (Oudenaarde) is a historic town in East Flanders, Belgium, known for its medieval architecture, tapestry production, and role in early modern European conflicts.
-
E.
Wommelgem
Wommelgem is a municipality in the Belgian province of Antwerp, known for its suburban character and proximity to the city of Antwerp.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de05c530148190b11704300bbd5f9b |
completed | April 14, 2026, 9:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdf06a3e208190a24e6cd9cb97e99c |
completed | May 8, 2026, 2:17 p.m. |
Created at: April 9, 2026, 10:14 p.m.