Triple
T21197317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marian Langiewicz |
E522359
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | January Uprising leader |
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: January Uprising leader Context triple: [Marian Langiewicz, instanceOf, January Uprising leader]
-
A.
Polish independence activist
chosen
A Polish independence activist is an individual who actively works—politically, socially, or culturally—to end foreign domination and secure Poland’s sovereignty and self-determination.
-
B.
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.
-
C.
Polish national movement
The Polish national movement was a broad, evolving effort by Poles—through political action, cultural revival, and armed struggle—to preserve their identity and ultimately restore an independent Polish state in the face of foreign partition and domination.
-
D.
Polish military leader
A Polish military leader is a high-ranking commander from Poland responsible for planning, directing, and overseeing military operations and the strategic use of armed forces in defense of the nation.
-
E.
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.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:11 p.m.