Triple

T37851701
Position Surface form Disambiguated ID Type / Status
Subject Broye-Vully District E944070 entity
Predicate contains P35 FINISHED
Object Chesalles-sur-Moudon
Chesalles-sur-Moudon is a small former municipality in the canton of Vaud in western Switzerland, situated in a rural area of the Swiss plateau.
E2245929 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: Chesalles-sur-Moudon | Statement: [Broye-Vully District, contains, Chesalles-sur-Moudon]
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: Chesalles-sur-Moudon
Triple: [Broye-Vully District, contains, Chesalles-sur-Moudon]
Generated description
Chesalles-sur-Moudon is a small former municipality in the canton of Vaud in western Switzerland, situated in a rural area of the Swiss plateau.

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_69f76eed4d9c81908b1b71ba9e3b61fe completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbb24ac0dc819099fb3a2d4551371c completed May 6, 2026, 9:27 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41041a31588190bee707f4e58c6c04 completed June 28, 2026, 11:23 a.m.
NEDg Description generation batch_6a4104850d7081908593da7a59d0d6b4 completed June 28, 2026, 11:24 a.m.
NED2 Entity disambiguation (via description) batch_6a4104eba3648190946cab1b84976a74 completed June 28, 2026, 11:26 a.m.
Created at: May 3, 2026, 4:19 p.m.