Triple
T10798501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strozzi family |
E254774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance 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 family Context triple: [Strozzi family, instanceOf, Renaissance family]
-
A.
noble family
A noble family is a socially and often legally recognized kinship group that holds hereditary titles, privileges, and status within a hierarchical society, typically associated with landownership, political influence, and longstanding lineage.
-
B.
medieval ruling family
A medieval ruling family is a hereditary dynasty that holds political power, land, and social authority over a realm, often legitimized by lineage, religion, and military strength.
-
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.
Italian dynasty
An Italian dynasty is a hereditary ruling family originating from Italy that maintains political, social, or economic power across multiple generations.
-
E.
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.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:17 p.m.