Triple
T2482140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Brunswick-Lüneburg |
E55841
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | title of nobility in the Holy Roman Empire |
C10175
|
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: title of nobility in the Holy Roman Empire Context triple: [Duke of Brunswick-Lüneburg, instanceOf, title of nobility in the Holy Roman Empire]
-
A.
Prince-elector of the Holy Roman Empire
A Prince-elector of the Holy Roman Empire was a high-ranking territorial ruler or ecclesiastical prince endowed with the exclusive right to participate in the election of the Holy Roman Emperor.
-
B.
Austrian noble
An Austrian noble is a member of the historical aristocracy of Austria, typically holding hereditary titles, land, and social privileges within the Habsburg and later Austrian realms.
-
C.
Russian imperial title
A Russian imperial title is a formal designation of rank and authority within the hierarchy of the Russian Empire, used by monarchs, nobility, and high officials to signify their status and governing roles.
-
D.
Russian imperial title
A Russian imperial title is a formal designation of rank and authority within the hierarchy of the Russian Empire, used by the monarch and members of the ruling dynasty.
-
E.
system of hereditary titles
A system of hereditary titles is a structured hierarchy of ranks and honors that are legally or socially passed down through family lines, typically from one generation to the next.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:45 p.m.