Triple
T17092650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caprini family |
E414763
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance Roman lineage |
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 Roman lineage Context triple: [Caprini family, instanceOf, Renaissance Roman lineage]
-
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.
ancient Roman family
An ancient Roman family (familia) was a hierarchical household unit centered on the paterfamilias, encompassing blood relatives, adopted members, slaves, and clients bound together by legal authority, religious rites, and shared social status.
-
C.
Italian dynasty
An Italian dynasty is a hereditary ruling family originating from Italy that maintains political, social, or economic power across multiple generations.
-
D.
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.
-
E.
Roman dynasty
A Roman dynasty is a succession of rulers from the same family or lineage who governed the Roman state over a continuous period, shaping its political, social, and cultural development.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:35 a.m.