Triple
T24849683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bismarck family estates |
E621851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aristocratic family properties |
C49173
|
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: aristocratic family properties Context triple: [Bismarck family estates, instanceOf, aristocratic family properties]
-
A.
aristocratic mansion
An aristocratic mansion is a grand, opulent residence historically owned by nobility or the elite, characterized by expansive grounds, elaborate architecture, and richly decorated interiors that symbolize wealth, power, and social status.
-
B.
landowning family
A landowning family is a kinship group whose social status, wealth, and influence are primarily derived from the ownership, control, and management of significant tracts of land across generations.
-
C.
former country estate
A former country estate is a large rural property that once served as the grand residential and agricultural domain of a wealthy owner, but has since been repurposed, subdivided, or fallen from its original status.
-
D.
manorial estate
A manorial estate is a large landed property in medieval and early modern Europe comprising the lord’s residence, peasant holdings, and common resources, organized as a self-sufficient economic and social unit under feudal control.
-
E.
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.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:20 a.m.