Triple
T8806189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rucellai family |
E209537
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Florentine patrician family |
C25091
|
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: Florentine patrician family Context triple: [Rucellai family, instanceOf, Florentine patrician family]
-
A.
Milanese patrician family
A Milanese patrician family is a historically prominent, aristocratic lineage from Milan that held social, political, and economic influence within the city’s elite ruling class.
-
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.
Dutch patrician family
A Dutch patrician family is a historically prominent, often urban-based lineage belonging to the higher bourgeois elite of the Netherlands, distinguished by long-standing social status, wealth, and influence in commerce, politics, or culture.
-
E.
Florentine political faction
A Florentine political faction is a historically rooted group within Florence’s civic life that organized around shared social, economic, or ideological interests to compete for power and influence in the city’s government and public affairs.
- 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_69ca836320e48190b5cf585b90a322c4 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:45 p.m.