Triple
T9805309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignacy Jan Paderewski |
E237939
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish independence activist |
C26863
|
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 independence activist Context triple: [Ignacy Jan Paderewski, instanceOf, Polish independence activist]
-
A.
Ukrainian independence activist
A Ukrainian independence activist is an individual who actively advocates, organizes, and mobilizes support for Ukraine’s political sovereignty, territorial integrity, and self-determination against foreign domination or influence.
-
B.
Korean independence activist
A Korean independence activist is an individual who actively resists foreign rule and advocates for Korea’s political sovereignty, cultural preservation, and national self-determination.
-
C.
Polish dissident
A Polish dissident is an individual from Poland who actively opposes and challenges an authoritarian or oppressive political system, often at personal risk, in pursuit of democratic freedoms and human rights.
-
D.
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.
-
E.
President of Poland in exile
The President of Poland in exile is the head of the Polish government operating outside the country’s territory, maintaining legal continuity and representing the Polish state when domestic sovereignty is compromised or occupied.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:29 p.m.