Triple
T10450104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nils von Kantzow |
E246398
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Swedish military officer |
C17496
|
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: Swedish military officer Context triple: [Nils von Kantzow, instanceOf, Swedish military officer]
-
A.
Swedish general
chosen
A Swedish general is a high-ranking military officer from Sweden responsible for leading large-scale army operations, shaping defense strategy, and overseeing the training, organization, and readiness of Swedish land forces.
-
B.
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.
-
C.
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.
-
D.
Swedish diplomat
A Swedish diplomat is an official representative of Sweden who conducts negotiations, fosters international relations, and advances Swedish political, economic, and cultural interests abroad.
-
E.
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.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:17 p.m.