Triple

T22212962
Position Surface form Disambiguated ID Type / Status
Subject Cervi E549001 entity
Predicate hasNotableBearer P458 FINISHED
Object Renato Cervi
Renato Cervi is an individual notable enough to be recognized as a prominent bearer of the surname Cervi.
E2289451 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: Renato Cervi | Statement: [Cervi, hasNotableBearer, Renato Cervi]
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: Renato Cervi
Triple: [Cervi, hasNotableBearer, Renato Cervi]
Generated description
Renato Cervi is an individual notable enough to be recognized as a prominent bearer of the surname Cervi.

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_69e11e3f7e04819089806d81d5ac431e completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12b2d607c81909511761b5563ddee completed April 28, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5b3d9a16cc8190b4b19eaebb3a2d77 completed July 18, 2026, 8:47 a.m.
NEDg Description generation batch_6a5b3ea2454081909cc8d85ce4498662 completed July 18, 2026, 8:51 a.m.
NED2 Entity disambiguation (via description) batch_6a5b40b69724819097275cec6e80413b completed July 18, 2026, 9 a.m.
Created at: April 16, 2026, 8:37 p.m.