Triple

T33982842
Position Surface form Disambiguated ID Type / Status
Subject Trivulzio family E871330 entity
Predicate member P10 FINISHED
Object Antonio Trivulzio
Antonio Trivulzio was an Italian nobleman and prelate from the influential Milanese Trivulzio family, active in politics and church affairs during the Renaissance.
E2081682 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: Antonio Trivulzio | Statement: [Trivulzio family, member, Antonio Trivulzio]
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: Antonio Trivulzio
Triple: [Trivulzio family, member, Antonio Trivulzio]
Generated description
Antonio Trivulzio was an Italian nobleman and prelate from the influential Milanese Trivulzio family, active in politics and church affairs during the Renaissance.

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_69f3499e964c8190b674b03f6f791b4b completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7038b75548190803c3916631e8638 completed May 3, 2026, 8:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36ae3ad7a0819084ee3c2461f4b619 completed June 20, 2026, 3:14 p.m.
NEDg Description generation batch_6a36b1fcb2fc81909b84219b6b700c2d completed June 20, 2026, 3:30 p.m.
NED2 Entity disambiguation (via description) batch_6a36b2f89c4881909af28784747136ad completed June 20, 2026, 3:34 p.m.
Created at: May 1, 2026, 1:50 a.m.