Triple
T17322890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burggraf |
E420604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German title of nobility |
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: German title of nobility Context triple: [Burggraf, instanceOf, German title of nobility]
-
A.
title of nobility in the Holy Roman Empire
chosen
A title of nobility in the Holy Roman Empire was a hereditary or granted rank (such as duke, prince, count, or baron) that conferred social status, legal privileges, and often territorial authority within the Empire’s feudal hierarchy.
-
B.
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.
-
C.
Hungarian noble title
A Hungarian noble title is a hereditary or granted rank within the historical social hierarchy of the Kingdom of Hungary, denoting status, privileges, and obligations among the nobility.
-
D.
Dutch noble title
A Dutch noble title is a hereditary or granted rank within the Netherlands’ nobility system, such as baron, count, or duke, conferring social prestige and sometimes traditional privileges but no formal political power today.
-
E.
Swedish noble title
A Swedish noble title is a hereditary or granted rank of nobility in Sweden, historically conferring social status, privileges, and often responsibilities within the Swedish aristocratic hierarchy.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:43 a.m.