Triple

T14576575
Position Surface form Disambiguated ID Type / Status
Subject Seneffe E342067 entity
Predicate locatedNear P294 FINISHED
Object Nivelles E341986 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: Nivelles | Statement: [Seneffe, locatedNear, Nivelles]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nivelles
Context triple: [Seneffe, locatedNear, Nivelles]
  • A. Nivelles chosen
    Nivelles is a historic town in present-day Belgium known for its medieval architecture, including the Romanesque Collegiate Church of Saint Gertrude.
  • B. 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.
  • C. Durbuy
    Durbuy is a small, picturesque town in the Belgian Ardennes often promoted as one of the “smallest cities in the world,” known for its medieval architecture and tourism.
  • D. Namur
    Namur is a historic Belgian city and the capital of Wallonia, located at the confluence of the Meuse and Sambre rivers.
  • E. 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.
  • 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_69d822dcc6248190bed689984bceb0e2 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb3f5ec448190b2ef887fdf7b633e completed April 14, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69febfcf67348190862c65faa1c815f0 completed May 9, 2026, 5:02 a.m.
Created at: April 10, 2026, 1:24 a.m.