Triple
T24849682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bismarck family estates |
E621851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic landed estates |
C49172
|
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: historic landed estates Context triple: [Bismarck family estates, instanceOf, historic landed estates]
-
A.
historic estate
A historic estate is a large, significant property—often including a grand residence, outbuildings, and landscaped grounds—that holds cultural, architectural, or historical importance from a past era.
-
B.
historic estate type
A historic estate type is a classification of large, historically significant residential properties characterized by their architectural style, period of construction, original function, and cultural or social importance.
-
C.
heritage estate
A heritage estate is a historically significant property, often including land, buildings, and cultural features, preserved for its architectural, cultural, or ancestral value.
-
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.
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.
- 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.