Triple
T38525109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Rożyński |
E922606
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish military commander |
C15351
|
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 military commander Context triple: [Roman Rożyński, instanceOf, Polish military commander]
-
A.
Polish military leader
chosen
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.
-
B.
Hungarian military leader
A Hungarian military leader is a high-ranking commander from Hungary responsible for planning, directing, and overseeing military operations and forces in defense of national or allied interests.
-
C.
Slovak military officer
A Slovak military officer is a commissioned member of Slovakia’s armed forces responsible for leading personnel, planning and executing military operations, and upholding national defense and security policies.
-
D.
Prussian general
A Prussian general is a high-ranking military officer of the historical Kingdom of Prussia, characterized by rigorous discipline, strategic planning, and leadership in organizing and commanding armies in war.
-
E.
Red Army commander
A Red Army commander is a high-ranking military officer responsible for planning, directing, and overseeing Soviet armed forces operations and personnel within the Red Army.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:32 p.m.