Triple
T20826458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benci family of Florence |
E512712
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance merchant dynasty |
C24056
|
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 merchant dynasty Context triple: [Benci family of Florence, instanceOf, Renaissance merchant dynasty]
-
A.
Venetian family
A Venetian family is a social unit rooted in Venice’s unique historical, cultural, and economic context, typically characterized by strong kinship ties, intergenerational traditions, and connections to the city’s maritime, mercantile, or artistic heritage.
-
B.
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.
-
C.
merchant dynasty
chosen
A merchant dynasty is a powerful family or lineage whose wealth, influence, and social status are built and sustained over generations through large-scale trade and commercial enterprises.
-
D.
Renaissance family
A Renaissance family is a kinship group in early modern Europe whose structure, roles, and daily life were shaped by humanist ideals, emerging social mobility, and the cultural, economic, and religious transformations of the 14th–17th centuries.
-
E.
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.
- 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:41 p.m.