Triple
T21301783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosimo de’ Pazzi |
E525082
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Pazzi family |
C44666
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: member of the Pazzi family Context triple: [Cosimo de’ Pazzi, instanceOf, member of the Pazzi family]
-
A.
member of the Borgia family
A member of the Borgia family is an individual belonging to the influential Italian-Spanish noble lineage renowned for its significant political, religious, and cultural impact during the Renaissance, often associated with power, intrigue, and controversy.
-
B.
Member of the House of Medici
A Member of the House of Medici is an individual belonging to the powerful Florentine banking and political dynasty that significantly influenced Renaissance art, culture, and European politics.
-
C.
Member of the House of Medici
A Member of the House of Medici is an individual belonging to the powerful Florentine banking and political dynasty that significantly influenced European finance, art, and politics from the 15th to 18th centuries.
-
D.
member of the Visconti dynasty
A member of the Visconti dynasty is an individual belonging to the powerful medieval and Renaissance noble family that ruled Milan and surrounding territories in northern Italy.
-
E.
member of the Barberini family
A member of the Barberini family is an individual belonging to the influential Italian noble lineage that rose to prominence in the 17th century, notably through Pope Urban VIII and their extensive political, cultural, and artistic patronage.
- F. None of above. chosen
Provenance (1 batch)
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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4:05 p.m.