Triple
T17843630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piotr Wysocki |
E445596
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish army officer |
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 army officer Context triple: [Piotr Wysocki, instanceOf, Polish army officer]
-
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.
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.
-
C.
Austro-Hungarian military officer
An Austro-Hungarian military officer was a commissioned leader in the armed forces of the Austro-Hungarian Empire, responsible for commanding troops, implementing imperial military policy, and upholding the dual monarchy’s authority across its diverse territories.
-
D.
Yugoslav military officer
A Yugoslav military officer is a commissioned member of the armed forces of the former Socialist Federal Republic of Yugoslavia, responsible for leading troops, planning and executing military operations, and upholding the doctrines and political-military objectives of the Yugoslav state.
-
E.
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.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:16 a.m.