Triple

T36287839
Position Surface form Disambiguated ID Type / Status
Subject Ecclesiastical province of Tours E893138 entity
Predicate hasSuffraganDiocese P17915 FINISHED
Object Diocese of Angers
The Diocese of Angers is a Roman Catholic ecclesiastical territory in western France centered on the city of Angers.
E2219955 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: Diocese of Angers | Statement: [Ecclesiastical province of Tours, hasSuffraganDiocese, Diocese of Angers]
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: Diocese of Angers
Triple: [Ecclesiastical province of Tours, hasSuffraganDiocese, Diocese of Angers]
Generated description
The Diocese of Angers is a Roman Catholic ecclesiastical territory in western France centered on the city of Angers.

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_69f76e4955c08190b8cfddca34fc0242 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b9e2c4748190bca80386b3456b0d completed May 3, 2026, 9:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40439fc7e08190949e1a95386fb841 completed June 27, 2026, 9:41 p.m.
NEDg Description generation batch_6a404403f5c881909238cd1411210315 completed June 27, 2026, 9:43 p.m.
NED2 Entity disambiguation (via description) batch_6a404b4327ec8190aa6f3c241f31e774 completed June 27, 2026, 10:14 p.m.
Created at: May 3, 2026, 4:09 p.m.