Triple
T15824616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Transylvania |
E383705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hungarian noble title |
C35862
|
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: Hungarian noble title Context triple: [Duke of Transylvania, instanceOf, Hungarian noble title]
-
A.
Hungarian noble
A Hungarian noble is a member of the historical aristocratic class of the Kingdom of Hungary, holding hereditary titles, land, and political privileges within the kingdom’s feudal and later constitutional systems.
-
B.
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.
-
C.
Polish noble office
A Polish noble office is a formal position or title within the historical governance and social hierarchy of the Polish–Lithuanian Commonwealth, held by members of the nobility (szlachta) and associated with specific administrative, judicial, or ceremonial duties.
-
D.
Portuguese noble title
A Portuguese noble title is a hereditary or granted rank of honor within Portugal's historical aristocratic hierarchy, denoting social status, privileges, and often territorial associations.
-
E.
title of nobility in the Holy Roman Empire
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.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:49 a.m.