Triple

T28447763
Position Surface form Disambiguated ID Type / Status
Subject Profondeville E715887 entity
Predicate hasMunicipalSections P10450 FINISHED
Object Bois-de-Villers
Bois-de-Villers is a village in Wallonia, Belgium, that forms one of the constituent districts of the municipality of Profondeville in the province of Namur.
E1907301 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: Bois-de-Villers | Statement: [Profondeville, hasMunicipalSections, Bois-de-Villers]
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: Bois-de-Villers
Triple: [Profondeville, hasMunicipalSections, Bois-de-Villers]
Generated description
Bois-de-Villers is a village in Wallonia, Belgium, that forms one of the constituent districts of the municipality of Profondeville in the province of Namur.

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_69efd6b44550819094ae991b553d9fc3 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f64e7019108190bb173f2168586ade completed May 2, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_6a276ecc2800819090b2bc6e61264e04 completed June 9, 2026, 1:39 a.m.
NEDg Description generation batch_6a276febe8e48190a61b0e20ac44ab06 completed June 9, 2026, 1:44 a.m.
NED2 Entity disambiguation (via description) batch_6a27708bfc588190abd7fa5039f5153a completed June 9, 2026, 1:46 a.m.
Created at: April 28, 2026, 1:50 a.m.