Triple
T12045167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carpzov family |
E286765
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early modern German 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: early modern German family Context triple: [Carpzov family, instanceOf, early modern German family]
-
A.
German family
A German family is a social unit typically consisting of parents and children living in Germany, shaped by German cultural norms, language, traditions, and legal frameworks around kinship and household life.
-
B.
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.
-
C.
German-Jewish family
A German-Jewish family is a kinship group whose members share both German cultural or national ties and Jewish religious, ethnic, or cultural heritage, shaped by the historical experiences of Jews in German-speaking lands.
-
D.
colonial-era family
A colonial-era family is a household unit living during a period of colonization, typically consisting of parents, children, and sometimes extended relatives, whose daily life, roles, and relationships are shaped by the social, economic, and political structures of the colonial system.
-
E.
German noble
A German noble is a member of the historical aristocratic class in German-speaking regions, traditionally holding hereditary titles, land, and social privileges within the feudal and later monarchical systems.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.