Triple
T22207187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tervuren |
E548842
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | Moorsel |
—
|
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: Moorsel | Statement: [Tervuren, hasSubdivision, Moorsel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moorsel Context triple: [Tervuren, hasSubdivision, Moorsel]
-
A.
Moorsel
chosen
Moorsel is a village in the Belgian province of East Flanders that forms part of the city of Aalst.
-
B.
Beersel
Beersel is a municipality in the Flemish Brabant province of Belgium, known for its historic Beersel Castle and traditional lambic and gueuze breweries.
-
C.
De Heurne
De Heurne is a small village in the Dutch province of Gelderland, located in the municipality of Aalten near the German border.
-
D.
Menterwolde
Menterwolde was a former municipality in the province of Groningen in the Netherlands that later became part of the municipality of Midden-Groningen.
-
E.
Maasbracht
Maasbracht is a town in the Dutch province of Limburg, known as an inland port and industrial center along the River Meuse.
- 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b2936a481909aa84c7983ed49ee |
completed | April 28, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:36 p.m.