Triple
T18928021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Siewierz |
E463025
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | title of nobility in the French Empire |
C39016
|
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 French Empire Context triple: [Prince of Siewierz, instanceOf, title of nobility in the French Empire]
-
A.
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.
-
B.
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.
-
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 the monarch and members of the ruling dynasty.
-
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.
imperial court title
chosen
An imperial court title is a formal designation granted within an empire’s ruling hierarchy that defines an individual’s rank, duties, and privileges in relation to the sovereign and the central administration.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:59 a.m.