Triple
T12931481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian forces in Siberia |
E309392
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italian Expeditionary Corps |
C24671
|
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: Italian Expeditionary Corps Context triple: [Italian forces in Siberia, instanceOf, Italian Expeditionary Corps]
-
A.
Italian army corps
chosen
An Italian army corps is a major military formation of the Italian Army, typically composed of multiple divisions and supporting units, organized to conduct large-scale operations under a unified command.
-
B.
brigade of the Italian Army
A brigade of the Italian Army is a large, modular land combat formation typically composed of several regiments or battalions, designed to conduct independent or joint operations within national and international missions.
-
C.
Italian Army infantry division
An Italian Army infantry division is a large, combined-arms military formation primarily composed of infantry units, supported by artillery, engineers, logistics, and command elements, organized to conduct sustained ground combat operations.
-
D.
Alpini division
An Alpini division is a specialized Italian Army mountain infantry formation trained and equipped for combat in alpine and other difficult mountainous terrains.
-
E.
Italian military organization
An Italian military organization is a structured entity within Italy’s armed forces responsible for planning, coordinating, and executing defense, security, and operational activities according to national and international directives.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:42 p.m.