Triple
T15558682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunswick-Bevern |
E370937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ducal principality |
C17262
|
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: ducal principality Context triple: [Brunswick-Bevern, instanceOf, ducal principality]
-
A.
Ernestine duchy
The Ernestine duchy refers to any of the small, historically fragmented German principalities in Thuringia ruled by the Ernestine branch of the Wettin dynasty after the partition of Saxony.
-
B.
hereditary principality
chosen
A hereditary principality is a sovereign or semi-sovereign territory ruled by a prince whose authority and title are passed down through a family line, typically by primogeniture or other dynastic succession rules.
-
C.
tribal duchies
Tribal duchies are semi-autonomous regional domains ruled by chieftains or nobles whose authority is rooted in kinship ties, customary law, and control over loosely organized tribal territories.
-
D.
Count of Nassau
The Count of Nassau was a noble title held by the rulers of the medieval and early modern County of Nassau in what is now western Germany, whose dynasty played a significant role in European politics, including founding the House of Orange-Nassau.
-
E.
Count of Luxembourg
A Count of Luxembourg is a noble title historically held by the feudal rulers of the County of Luxembourg, signifying territorial lordship, aristocratic status, and dynastic authority within the medieval and early modern European nobility.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:09 a.m.