Triple

T9935376
Position Surface form Disambiguated ID Type / Status
Subject Lontzen E192745 entity
Predicate borderedBy P224 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: [Lontzen, borderedBy, Raeren]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Raeren
Context triple: [Lontzen, borderedBy, Raeren]
  • A. Raeren chosen
    Raeren is a municipality in eastern Belgium known for its German-speaking population and historical stoneware pottery tradition.
  • B. Braine-l'Alleud
    Braine-l'Alleud is a municipality in Walloon Brabant, Belgium, known for encompassing much of the historic Waterloo battlefield.
  • C. Vandoeuvres
    Vandoeuvres is a small, affluent residential municipality located near the city of Geneva in western Switzerland.
  • D. Gosselies
    Gosselies is a district of the city of Charleroi in Wallonia, Belgium, known for its proximity to Brussels South Charleroi Airport and its industrial and aeronautical activities.
  • E. Mont-Saint-Guibert
    Mont-Saint-Guibert is a municipality in the province of Walloon Brabant in the French-speaking Walloon region of Belgium.
  • 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_69ca82dd978c8190947124ab0d3315ac completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb5e263208190b6ea8b8b4e29805d completed April 2, 2026, 12:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69d369657ecc81909d0c710ca919602e completed April 6, 2026, 8:05 a.m.
Created at: March 30, 2026, 8:44 p.m.