Triple

T31901596
Position Surface form Disambiguated ID Type / Status
Subject Diocese of Metz E814436 entity
Predicate metropolitanSee P16486 FINISHED
Object Archdiocese of Besançon
The Archdiocese of Besançon is a historic Latin Catholic metropolitan archdiocese in eastern France that oversees several suffragan dioceses in the region.
E1021698 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: Archdiocese of Besançon | Statement: [Diocese of Metz, metropolitanSee, Archdiocese of Besançon]
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: Archdiocese of Besançon
Triple: [Diocese of Metz, metropolitanSee, Archdiocese of Besançon]
Generated description
The Archdiocese of Besançon is a historic Latin Catholic metropolitan archdiocese in eastern France that oversees several suffragan dioceses in the region.

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_69f348f04d7881909537fc9e7cbc670e completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b168342481909e2e0d4fd99378d6 completed May 3, 2026, 2:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a33e87ca0188190b579205586ff1d14 completed June 18, 2026, 12:45 p.m.
NEDg Description generation batch_6a33e954d89881908ea05c9e466780fa completed June 18, 2026, 12:49 p.m.
NED2 Entity disambiguation (via description) batch_6a342c695e348190957d2cf24a4bc080 completed June 18, 2026, 5:35 p.m.
Created at: April 30, 2026, 11:59 p.m.