Triple
T20959575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbian Supreme Command |
E516201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supreme military headquarters |
C33841
|
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: supreme military headquarters Context triple: [Serbian Supreme Command, instanceOf, supreme military headquarters]
-
A.
Allied military authority
An Allied military authority is a governing body established by cooperating allied nations' armed forces to administer, control, and coordinate military and sometimes civil affairs in occupied or liberated territories during and immediately after conflict.
-
B.
Wehrmacht headquarters
The Wehrmacht headquarters was the central command authority of Nazi Germany's unified armed forces, responsible for strategic planning, coordination, and direction of military operations during World War II.
-
C.
inter-Allied military staff
chosen
A collaborative body of military officers from multiple allied nations responsible for joint strategic planning, coordination, and command of combined armed forces.
-
D.
Wehrmacht high command
The Wehrmacht high command was the central military leadership of Nazi Germany responsible for planning, directing, and coordinating the operations of the German armed forces during the Second World War.
-
E.
Allied occupation body
An Allied occupation body is an administrative authority established by victorious Allied powers to govern, oversee reconstruction, and implement political, economic, and legal reforms in a defeated or occupied territory following conflict.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 1:30 p.m.