Triple

T33283156
Position Surface form Disambiguated ID Type / Status
Subject Saint Prosdocimus E852103 entity
Predicate nameInItalian P17612 FINISHED
Object San Prosdocimo
San Prosdocimo is the Italian name for Saint Prosdocimus, a revered early Christian bishop and patron saint traditionally associated with the city of Padua.
E2042921 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: San Prosdocimo | Statement: [Saint Prosdocimus, nameInItalian, San Prosdocimo]
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: San Prosdocimo
Triple: [Saint Prosdocimus, nameInItalian, San Prosdocimo]
Generated description
San Prosdocimo is the Italian name for Saint Prosdocimus, a revered early Christian bishop and patron saint traditionally associated with the city of Padua.

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_69f349653da08190819876015a298fdb completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6de6842cc8190a13788bec449102e completed May 3, 2026, 5:34 a.m.
NED1 Entity disambiguation (via context triple) batch_6a353925d38c819091cab70d064e624f completed June 19, 2026, 12:42 p.m.
NEDg Description generation batch_6a3539c0daf88190b8f926d01b6c745e completed June 19, 2026, 12:44 p.m.
NED2 Entity disambiguation (via description) batch_6a353a2156248190b503b83c3689e5de completed June 19, 2026, 12:46 p.m.
Created at: May 1, 2026, 1:32 a.m.