Triple
T21335847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belfry of Roesbrugge-Haringe |
E526043
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Poperinge |
—
|
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: Poperinge | Statement: [Belfry of Roesbrugge-Haringe, locatedIn, Poperinge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Poperinge Context triple: [Belfry of Roesbrugge-Haringe, locatedIn, Poperinge]
-
A.
Poperinge
chosen
Poperinge is a Belgian town in West Flanders known for its hop-growing tradition and historic role as a rear-area center during World War I.
-
B.
Torhout
Torhout is a small city in West Flanders, Belgium, known for its educational institutions and its location near Bruges.
-
C.
Wommelgem
Wommelgem is a municipality in the Belgian province of Antwerp, known for its suburban character and proximity to the city of Antwerp.
-
D.
Beringen
Beringen is a municipality in northern Switzerland known for its location near the Rhine and its surrounding vineyards and rural landscapes.
-
E.
Beringen
Beringen is a city and municipality in the Belgian province of Limburg, known for its coal mining heritage and the be-MINE industrial heritage site.
- 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e898d6fcbc8190b83d9cfc9b4ca123 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 4:43 p.m.