Triple

T33367221
Position Surface form Disambiguated ID Type / Status
Subject Villars-sur-Glâne E854386 entity
Predicate region P40 FINISHED
Object Sarine region
The Sarine region is an administrative district in the canton of Fribourg, Switzerland, centered around the city of Fribourg and encompassing several surrounding municipalities.
E2047965 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: Sarine region | Statement: [Villars-sur-Glâne, region, Sarine region]
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: Sarine region
Triple: [Villars-sur-Glâne, region, Sarine region]
Generated description
The Sarine region is an administrative district in the canton of Fribourg, Switzerland, centered around the city of Fribourg and encompassing several surrounding municipalities.

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_69f3496bda8c8190bfc8fade9d1b791c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6dfd37cf88190a8dcca57964f66bd completed May 3, 2026, 5:40 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3552190ad881908112a259f3980912 completed June 19, 2026, 2:28 p.m.
NEDg Description generation batch_6a35538978cc819090a53adeaab86213 completed June 19, 2026, 2:34 p.m.
NED2 Entity disambiguation (via description) batch_6a355a5fca888190896612ed7c88715b completed June 19, 2026, 3:04 p.m.
Created at: May 1, 2026, 1:35 a.m.