Triple
T28185235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Arco-Zinneberg |
E716159
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bavarian noble house |
C24859
|
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: Bavarian noble house Context triple: [House of Arco-Zinneberg, instanceOf, Bavarian noble house]
-
A.
German princely dynasty
A German princely dynasty is a hereditary ruling family from the German-speaking regions of Europe that historically held princely titles, governed territories, and played significant roles in regional and imperial politics.
-
B.
Alsatian noble house
An Alsatian noble house is an aristocratic family originating from the Alsace region, historically holding hereditary titles, lands, and political influence within the shifting sovereignties of France and the Holy Roman Empire.
-
C.
Nuremberg dynasty
The Nuremberg dynasty is a conceptual class representing a lineage of influential families or rulers centered in or originating from Nuremberg, whose power, heritage, and socio-political impact persist across multiple generations.
-
D.
German noble family branch
chosen
A German noble family branch is a distinct lineage or subdivision of a larger aristocratic house in German-speaking regions, typically defined by shared ancestry, territorial holdings, and hereditary titles.
-
E.
House of Wettin
The House of Wettin is a historic European noble dynasty originating in Saxony that produced numerous princes, electors, kings, and other rulers across central and northern Europe from the Middle Ages onward.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:22 p.m.