Triple

T31672391
Position Surface form Disambiguated ID Type / Status
Subject Gruyères E808304 entity
Predicate governedBy P46 FINISHED
Object municipal council of Gruyères
The municipal council of Gruyères is the local governing body responsible for administering and managing public affairs in the Swiss town of Gruyères.
E1972311 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: municipal council of Gruyères | Statement: [Gruyères, governedBy, municipal council of Gruyères]
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: municipal council of Gruyères
Triple: [Gruyères, governedBy, municipal council of Gruyères]
Generated description
The municipal council of Gruyères is the local governing body responsible for administering and managing public affairs in the Swiss town of Gruyères.

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_69f348dbeef4819080b446a7feb6340b completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6aa500aa48190b3d04374ba19ce86 completed May 3, 2026, 1:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b79f4b4708190bf579fc7fa4bf0e4 completed June 12, 2026, 3:16 a.m.
NEDg Description generation batch_6a2b7e45bc1c8190bb2bf6c4299e45f1 completed June 12, 2026, 3:34 a.m.
NED2 Entity disambiguation (via description) batch_6a2b7ea8b1e081909ed864667822e1f3 completed June 12, 2026, 3:36 a.m.
Created at: April 30, 2026, 11:01 p.m.