Triple
T27519686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Berg-Altena |
E694671
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval German 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: medieval German noble house Context triple: [House of Berg-Altena, instanceOf, medieval German noble house]
-
A.
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.
-
B.
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.
-
C.
medieval English noble dynasty
A medieval English noble dynasty is a powerful hereditary family line that held titles, lands, and political influence across generations in England during the Middle Ages.
-
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.
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.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:20 p.m.