Triple
T10530645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gavere |
E248431
|
entity |
| Predicate | hasConstituentVillage |
P4011
|
FINISHED |
| Object | Gavere (village) |
E248431
|
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: Gavere (village) | Statement: [Gavere, hasConstituentVillage, Gavere (village)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gavere (village) Context triple: [Gavere, hasConstituentVillage, Gavere (village)]
-
A.
Gavere-Semmerzake
Gavere-Semmerzake is a Belgian military air base used by the Belgian Air Force.
-
B.
Gavere
chosen
Gavere is a municipality in the Belgian province of East Flanders, known for its rural character and several constituent villages.
-
C.
Horebeke
Horebeke is a small rural municipality in the Flemish Ardennes region of East Flanders, Belgium.
-
D.
Groesbeek
Groesbeek is a village in the Dutch province of Gelderland, known for its hilly landscape, World War II history, and wine production.
-
E.
Veurne
Veurne is a historic town in western Belgium known for its well-preserved medieval center and Flemish Renaissance architecture.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5190da7f081908c38b5964a567e37 |
completed | April 7, 2026, 2:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d90e3caf4c8190b19199f1a68a00de |
completed | April 10, 2026, 2:50 p.m. |
Created at: April 6, 2026, 12:30 p.m.