Triple

T33835744
Position Surface form Disambiguated ID Type / Status
Subject Pietro Paolo Tedesco E867226 entity
Predicate hasGivenName P17 FINISHED
Object Pietro Paolo
Pietro Paolo is an Italian given name traditionally used in reference to men, often reflecting Christian heritage through its combination of the names Peter and Paul.
E2115210 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: Pietro Paolo | Statement: [Pietro Paolo Tedesco, hasGivenName, Pietro Paolo]
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: Pietro Paolo
Triple: [Pietro Paolo Tedesco, hasGivenName, Pietro Paolo]
Generated description
Pietro Paolo is an Italian given name traditionally used in reference to men, often reflecting Christian heritage through its combination of the names Peter and Paul.

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_69f34992ad40819087760ed939bd2a7a completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7002dc8588190bb294f05e6f36d30 completed May 3, 2026, 7:58 a.m.
NED1 Entity disambiguation (via context triple) batch_6a377928da608190a179653af64b0d35 completed June 21, 2026, 5:39 a.m.
NEDg Description generation batch_6a377a18f8308190851b20da04cabc34 completed June 21, 2026, 5:43 a.m.
NED2 Entity disambiguation (via description) batch_6a377af6ab048190b572cefa83ec6dda completed June 21, 2026, 5:47 a.m.
Created at: May 1, 2026, 1:47 a.m.