Triple
T34749070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siemowit |
E1001718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish legendary figure |
C31828
|
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: Polish legendary figure Context triple: [Siemowit, instanceOf, Polish legendary figure]
-
A.
Polish legendary ruler
chosen
A Polish legendary ruler is a mythic or semi-mythic sovereign from Poland’s early tradition, known primarily through folklore, chronicles, and national legends rather than verified historical records.
-
B.
national hero of Poland
A national hero of Poland is an individual, often historical or military, who is widely revered for extraordinary acts of courage, sacrifice, or leadership that significantly advanced Polish independence, freedom, or cultural identity.
-
C.
Tatar national hero
A Tatar national hero is a historically or culturally significant figure who embodies the Tatar people's ideals of courage, resilience, and identity, often celebrated in folklore, literature, and collective memory.
-
D.
Polish prince
A Polish prince is a male member of the historical Polish nobility or royal family, often holding hereditary titles, lands, and political influence within the Polish–Lithuanian Commonwealth or its predecessor states.
-
E.
Polish person
A Polish person is an individual who identifies with or holds citizenship of Poland, typically sharing its cultural, historical, and linguistic heritage.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.