Triple
T15102254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casimir I of Kuyavia |
E360697
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Polish noble |
C32456
|
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 noble Context triple: [Casimir I of Kuyavia, instanceOf, medieval Polish noble]
-
A.
Polish–Lithuanian nobleman
A Polish–Lithuanian nobleman was a member of the szlachta elite of the Polish–Lithuanian Commonwealth, holding hereditary privileges, political rights, and often landed estates within its multiethnic realm.
-
B.
Polish duke
A Polish duke is a high-ranking nobleman in Poland, historically holding significant territorial authority, political influence, and social prestige within the Polish–Lithuanian Commonwealth or earlier Piast and Jagiellonian realms.
-
C.
medieval European noble
chosen
A medieval European noble is a high-ranking member of the feudal aristocracy who holds land granted by a monarch in exchange for military service and governance over vassals and peasants.
-
D.
Bohemian nobleman
A Bohemian nobleman is an aristocrat from the historical Kingdom of Bohemia, distinguished by hereditary titles, landownership, and a role in the region’s political and cultural life.
-
E.
Polish noblewoman
A Polish noblewoman is a female member of the historical Polish szlachta, typically associated with landownership, social privilege, and participation in the political and cultural life of the Polish–Lithuanian Commonwealth.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:05 a.m.