Triple
T10840432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignacy Daszyński |
E255870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish socialist politician |
C28875
|
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 socialist politician Context triple: [Ignacy Daszyński, instanceOf, Polish socialist politician]
-
A.
Czechoslovak politician
A Czechoslovak politician is a public figure who held governmental or party office in the former state of Czechoslovakia, influencing its domestic and foreign policies before its dissolution in 1993.
-
B.
Belarusian politician
A Belarusian politician is an individual actively involved in the governance, political decision-making, or public administration of Belarus, typically holding or seeking a public office within its political system.
-
C.
East German politician
An East German politician is a public official or political figure who was active in the governance, administration, or party structures of the former German Democratic Republic (GDR) before its reunification with West Germany in 1990.
-
D.
Japanese socialist politician
A Japanese socialist politician is a public official in Japan who advocates for and implements policies based on socialist principles such as social equality, workers’ rights, and public welfare within the country’s political system.
-
E.
Hungarian politician
A Hungarian politician is a public figure who participates in the governance and political decision-making processes of Hungary, typically by holding or seeking elected or appointed office at the local, regional, or national level.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:19 p.m.