Triple
T31955643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erbach-Schönberg |
E815896
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mediatized 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: mediatized German noble house Context triple: [Erbach-Schönberg, instanceOf, mediatized German 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.
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.
-
C.
9th-century German noble
A 9th-century German noble was a member of the hereditary warrior aristocracy in the East Frankish realms, holding land and local authority in exchange for military service and loyalty to the Carolingian king or his successors.
-
D.
member of German nobility
A member of German nobility is an individual belonging to a historically privileged social class in German-speaking regions, typically holding hereditary titles, land, and social status recognized under traditional aristocratic systems.
-
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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:08 a.m.