Triple
T27301869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl VI, Prince of Schwarzenberg |
E688930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Schwarzenberg family |
C52710
|
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: member of the Schwarzenberg family Context triple: [Karl VI, Prince of Schwarzenberg, instanceOf, member of the Schwarzenberg family]
-
A.
member of the House of Lobkowicz
A member of the House of Lobkowicz is an individual belonging by birth or adoption to the historic Czech noble family of Lobkowicz, associated with significant political, cultural, and economic influence in Central Europe.
-
B.
member of the House of Leuchtenberg
A member of the House of Leuchtenberg is an individual belonging by birth or lawful succession to the noble family founded by Eugène de Beauharnais, historically associated with titles and roles within European aristocracy.
-
C.
member of the House of Reuss
A member of the House of Reuss is an individual belonging to the historic German princely family that ruled various small states in Thuringia, traditionally naming all male members Heinrich (Henry).
-
D.
member of von Weizsäcker family
A member of the von Weizsäcker family is an individual belonging to the prominent German lineage known for its influential roles in science, philosophy, politics, and public life.
-
E.
member of the Babenberg dynasty
A member of the Babenberg dynasty is an individual belonging to the medieval noble family that ruled Austria and parts of Central Europe from the 10th to the mid-13th century.
- 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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:22 a.m.