Triple

T8956464
Position Surface form Disambiguated ID Type / Status
Subject Uccle E213481 entity
Predicate hasSubdivision P747 FINISHED
Object Moensberg
Moensberg is a residential neighborhood in the municipality of Uccle in the Brussels-Capital Region of Belgium.
E774141 NE FINISHED

How this triple was built (4 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: Moensberg | Statement: [Uccle, hasSubdivision, Moensberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moensberg
Context triple: [Uccle, hasSubdivision, Moensberg]
  • A. Bütgenbach
    Bütgenbach is a municipality in eastern Belgium’s German-speaking Community, known for its scenic lake, outdoor recreation, and proximity to the strategic Elsenborn Ridge.
  • B. Mechernich
    Mechernich is a small town in the Eifel region of North Rhine-Westphalia, Germany, known for its rural landscape and cultural landmarks such as the Bruder Klaus Field Chapel.
  • C. Morlanwelz
    Morlanwelz is a municipality in the Hainaut province of Wallonia, Belgium, known as part of the industrial region of the Charleroi basin.
  • D. Ottignies
    Ottignies is a town in central Belgium, in Walloon Brabant, known as a regional transport hub on the rail route between Brussels and Namur.
  • E. Bottendorf
    Bottendorf is a locality in the German state of Thuringia that historically existed within the German Empire.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Moensberg
Triple: [Uccle, hasSubdivision, Moensberg]
Generated description
Moensberg is a residential neighborhood in the municipality of Uccle in the Brussels-Capital Region of Belgium.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Moensberg
Target entity description: Moensberg is a residential neighborhood in the municipality of Uccle in the Brussels-Capital Region of Belgium.
  • A. Bütgenbach
    Bütgenbach is a municipality in eastern Belgium’s German-speaking Community, known for its scenic lake, outdoor recreation, and proximity to the strategic Elsenborn Ridge.
  • B. Mechernich
    Mechernich is a small town in the Eifel region of North Rhine-Westphalia, Germany, known for its rural landscape and cultural landmarks such as the Bruder Klaus Field Chapel.
  • C. Morlanwelz
    Morlanwelz is a municipality in the Hainaut province of Wallonia, Belgium, known as part of the industrial region of the Charleroi basin.
  • D. Ottignies
    Ottignies is a town in central Belgium, in Walloon Brabant, known as a regional transport hub on the rail route between Brussels and Namur.
  • E. Bottendorf
    Bottendorf is a locality in the German state of Thuringia that historically existed within the German Empire.
  • F. None of above. chosen

Provenance (5 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_69ca8399ad2081909f8fa41d4314c215 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6728965881908e9f14aaee0c5a18 completed April 1, 2026, 12:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfeb3680f88190a977ac4c103423f2 completed April 3, 2026, 4:30 p.m.
NEDg Description generation batch_69cfecad4c9081908598b47fce635d2e completed April 3, 2026, 4:37 p.m.
NED2 Entity disambiguation (via description) batch_69cfed0cb524819097af07d80ed537af completed April 3, 2026, 4:38 p.m.
Created at: March 30, 2026, 7 p.m.