Triple
T37846597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felice Brancacci |
E943918
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Brancacci family |
C66155
|
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 Brancacci family Context triple: [Felice Brancacci, instanceOf, member of the Brancacci family]
-
A.
member of the Rucellai family
A member of the Rucellai family is an individual belonging to the prominent Florentine noble lineage known for its influence in politics, commerce, and patronage of Renaissance art and architecture.
-
B.
member of the Pazzi family
A member of the Pazzi family is an individual belonging by birth or marriage to the historically influential Florentine noble house known for its political ambitions, banking activities, and role in the Pazzi Conspiracy against the Medici.
-
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 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.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.