Triple
T29948100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rucellai |
E760693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance Florentine 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: Renaissance Florentine family Context triple: [Rucellai, instanceOf, Renaissance Florentine family]
-
A.
Florentine patrician family
chosen
A Florentine patrician family is a prominent, aristocratic lineage in Renaissance Florence whose wealth, political influence, and social status shaped the city’s governance, culture, and economic life.
-
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.
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.
-
E.
Florentine guild
A Florentine guild was a powerful medieval and Renaissance association of artisans, merchants, or professionals in Florence that regulated trade, protected members’ interests, and played a central role in the city’s economic and political life.
- F. None of above.
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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:24 p.m.