Triple
T17516227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Kettler |
E426575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Baltic German noble family |
C22805
|
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: Baltic German noble family Context triple: [House of Kettler, instanceOf, Baltic German noble family]
-
A.
Baltic German noble
chosen
A Baltic German noble was a member of the German-speaking hereditary elite in the Baltic provinces (primarily present-day Estonia and Latvia), historically holding significant land, political power, and cultural influence under various ruling empires.
-
B.
Prussian aristocratic family
A Prussian aristocratic family is a noble lineage rooted in the historical Kingdom of Prussia, characterized by hereditary titles, landed estates, military and bureaucratic service, and adherence to traditional social hierarchies and customs.
-
C.
Polish-Lithuanian noble family
A Polish-Lithuanian noble family is a lineage belonging to the historical szlachta estate of the Polish-Lithuanian Commonwealth, characterized by hereditary titles, coats of arms, landholdings, and participation in the region’s political and social life.
-
D.
Georgian noble family
A Georgian noble family is a hereditary lineage from Georgia historically endowed with social prestige, land, and political influence within the country’s aristocratic hierarchy.
-
E.
Swedish noble family
A Swedish noble family is a lineage of individuals in Sweden historically granted hereditary noble status, often holding titles, estates, and social privileges recognized by the Swedish nobility system.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:49 a.m.