Triple

T13048492
Position Surface form Disambiguated ID Type / Status
Subject Condroz E327385 entity
Predicate containsSettlement P847 FINISHED
Object Morlanwelz E762742 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: Morlanwelz | Statement: [Condroz, containsSettlement, Morlanwelz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Morlanwelz
Context triple: [Condroz, containsSettlement, Morlanwelz]
  • A. Morlanwelz chosen
    Morlanwelz is a municipality in the Hainaut province of Wallonia, Belgium, known as part of the industrial region of the Charleroi basin.
  • B. Erquelinnes
    Erquelinnes is a municipality in the province of Hainaut in Wallonia, Belgium, located near the French border along the Sambre River.
  • C. Martelange
    Martelange is a small Belgian town known for straddling the border with Luxembourg and serving as a local commercial and transit hub.
  • D. Comines
    Comines is a town situated along the Lys River in the historic Flanders region on the border between France and Belgium.
  • E. Moensberg
    Moensberg is a residential neighborhood in the municipality of Uccle in the Brussels-Capital 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_69d8076e64308190904fb5c93517c901 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d980b8811c81908577f092e2736610 completed April 10, 2026, 10:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7941e0560819080eee43a9ed0e1bb completed May 3, 2026, 6:29 p.m.
Created at: April 9, 2026, 8:57 p.m.