Triple

T2774547
Position Surface form Disambiguated ID Type / Status
Subject Eupen-Malmedy region E61536 entity
Predicate hasMunicipality P847 FINISHED
Object Raeren E258135 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: Raeren | Statement: [Eupen-Malmedy region, hasMunicipality, Raeren]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Raeren
Context triple: [Eupen-Malmedy region, hasMunicipality, Raeren]
  • A. Raeren chosen
    Raeren is a municipality in eastern Belgium known for its German-speaking population and historical stoneware pottery tradition.
  • B. Vandoeuvres
    Vandoeuvres is a small, affluent residential municipality located near the city of Geneva in western Switzerland.
  • C. Binche
    Binche is a historic town in the Walloon region of Belgium, renowned for its well-preserved medieval architecture and its UNESCO-recognized Carnival of Binche.
  • D. Wavre
    Wavre is a town in central Belgium that serves as the capital of Walloon Brabant and is known for hosting the Walibi Belgium amusement park.
  • E. Verviers
    Verviers is a city in eastern Belgium known historically for its textile industry and as a regional center in the province of Liège.
  • 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_69ab4b7cd13481909174bca9809ed259 completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdd7f9570819087f1b1cb59d68586 completed March 7, 2026, 8:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69b3608166888190a4bf75f865e42f45 completed March 13, 2026, 12:55 a.m.
Created at: March 6, 2026, 9:57 p.m.