Triple

T22657313
Position Surface form Disambiguated ID Type / Status
Subject De Kempen E559261 entity
Predicate hasSettlement P1068 FINISHED
Object Beerse 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: Beerse | Statement: [De Kempen, hasSettlement, Beerse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beerse
Context triple: [De Kempen, hasSettlement, Beerse]
  • A. Overijse
    Overijse is a municipality in the Flemish Brabant province of Belgium, known for its green residential character and extensive vineyards.
  • B. Beerse, Belgium chosen
    Beerse, Belgium is a municipality in the Flemish region best known as the home base of Janssen Pharmaceuticals, a major global pharmaceutical company.
  • C. Beersel
    Beersel is a municipality in the Flemish Brabant province of Belgium, known for its historic Beersel Castle and traditional lambic and gueuze breweries.
  • 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_69e245489dd88190b1f674acf61c8769 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1765c62bc8190b3fcde76d6b6dfb6 completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 3:06 p.m.