Triple
T29899425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pazzi family |
E759369
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance-era family |
C28345
|
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-era family Context triple: [Pazzi family, instanceOf, Renaissance-era family]
-
A.
Renaissance family
chosen
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.
-
B.
Renaissance-era figure
A Renaissance-era figure is an individual from roughly the 14th to 17th centuries who contributed to the period’s revival of classical learning, artistic innovation, scientific inquiry, or humanist thought.
-
C.
Renaissance figure
A Renaissance figure is a historically significant individual from roughly the 14th to 17th centuries who contributed to the revival of classical learning and the flourishing of arts, sciences, and humanist thought in Europe.
-
D.
17th-century Italian aristocracy
The 17th-century Italian aristocracy comprised powerful noble families who controlled fragmented city-states and territories through landownership, patronage, and courtly culture, blending feudal traditions with Baroque-era political and artistic influence.
-
E.
Tudor-era noble
A Tudor-era noble is a high-ranking member of England’s aristocracy during the Tudor dynasty (1485–1603), wielding political influence, land-based wealth, and social prestige within a rigid hierarchical court and feudal system.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:06 p.m.