Triple

T31220454
Position Surface form Disambiguated ID Type / Status
Subject Luxeuil Abbey E795994 entity
Predicate associatedWithSaint P2830 FINISHED
Object Donatus of Besançon
Donatus of Besançon was a 7th-century bishop and saint in the Frankish church, venerated for his piety and leadership in the region around Besançon.
E1956630 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: Donatus of Besançon | Statement: [Luxeuil Abbey, associatedWithSaint, Donatus 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: Donatus of Besançon
Triple: [Luxeuil Abbey, associatedWithSaint, Donatus of Besançon]
Generated description
Donatus of Besançon was a 7th-century bishop and saint in the Frankish church, venerated for his piety and leadership in the region around Besançon.

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_69f224d9d52c8190a61f68ded37fa755 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69c4d35848190bd5a2dd81851bea3 completed May 3, 2026, 12:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2a1e1cae7081908f4ca6ec3cf661d8 completed June 11, 2026, 2:31 a.m.
NEDg Description generation batch_6a2a5a88a63081908ea7e8241c88d4f1 completed June 11, 2026, 6:49 a.m.
NED2 Entity disambiguation (via description) batch_6a2a5ade22448190b3998f6efd3672f0 completed June 11, 2026, 6:51 a.m.
Created at: April 29, 2026, 9:10 p.m.