Triple
T35550880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Schweidnitz |
E1027357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Silesian noble family |
C62224
|
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: Silesian noble family Context triple: [von Schweidnitz, instanceOf, Silesian noble family]
-
A.
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.
-
B.
Moravian noble family
A Moravian noble family is an aristocratic lineage originating from the historical region of Moravia, holding hereditary titles, estates, and social influence within the political and cultural structures of Central Europe.
-
C.
Hungarian noble family
A Hungarian noble family is a historically recognized lineage within the Kingdom of Hungary’s aristocracy, holding hereditary titles, lands, and social privileges passed down through generations.
-
D.
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.
-
E.
Cossack noble family
A Cossack noble family is a lineage descended from or elevated within the Cossack military estate, holding hereditary status, land, and social privileges in Cossack communities and broader regional nobility.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.