Triple

T28017295
Position Surface form Disambiguated ID Type / Status
Subject House of Mancini E707581 entity
Predicate hasMember P10 FINISHED
Object Michele Lorenzo Mancini
Michele Lorenzo Mancini is a member of the noble House of Mancini, an Italian aristocratic family historically associated with influence and prestige.
E1799749 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: Michele Lorenzo Mancini | Statement: [House of Mancini, hasMember, Michele Lorenzo Mancini]
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: Michele Lorenzo Mancini
Triple: [House of Mancini, hasMember, Michele Lorenzo Mancini]
Generated description
Michele Lorenzo Mancini is a member of the noble House of Mancini, an Italian aristocratic family historically associated with influence and prestige.

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_69ef96baf3a881909a2b63844185dddd completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f63c087c5c81908a4bda4294a61f1d completed May 2, 2026, 6:01 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15b8a456148190b2b595132ebe44f7 completed May 26, 2026, 3:13 p.m.
NEDg Description generation batch_6a15ba0eed048190aaaf5b9d5045ff5d completed May 26, 2026, 3:19 p.m.
NED2 Entity disambiguation (via description) batch_6a15bb03ba088190bd62a5a9de0115f5 completed May 26, 2026, 3:23 p.m.
Created at: April 27, 2026, 8:07 p.m.