Triple
T17854167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcantonio VII Borghese |
E445886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Borghese family |
C39208
|
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 Borghese family Context triple: [Marcantonio VII Borghese, instanceOf, member of the Borghese family]
-
A.
member of the Farnese family
A member of the Farnese family is an individual belonging to the influential Italian noble dynasty that rose to prominence in the Renaissance through political power, military leadership, and significant patronage of the arts and architecture.
-
B.
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.
-
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 Renaissance art, culture, and European politics.
-
D.
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.
-
E.
member of the Vespasia family
A member of the Vespasia family is an individual belonging to a distinguished lineage characterized by its shared heritage, traditions, and familial identity.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:17 a.m.