Triple
T35125121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Inowrocław |
E1014280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Polish princely title |
C43995
|
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: medieval Polish princely title Context triple: [Duke of Inowrocław, instanceOf, medieval Polish princely title]
-
A.
Polish noble title
chosen
A Polish noble title is a hereditary or granted rank within the historical Polish–Lithuanian nobility (szlachta), denoting social status, privileges, and often specific duties in the political and military hierarchy.
-
B.
Silesian ducal title
A Silesian ducal title is a hereditary noble rank held by rulers of the historical Silesian duchies, signifying territorial authority and dynastic status within the region of Silesia.
-
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.
medieval Rus’ title
A medieval Rus’ title is a formal designation of rank, office, or nobility used in the political and social hierarchy of the East Slavic principalities from roughly the 9th to the 15th centuries.
-
E.
High Duke of Poland
The High Duke of Poland was the senior prince who, under the 12th–13th century Piast succession system, held supreme authority over the Polish realm and its subordinate duchies.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.