Triple
T29617450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Expeditionary Corps in Russia |
E754899
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italian military formation |
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 military formation Context triple: [Italian Expeditionary Corps in Russia, instanceOf, Italian military formation]
-
A.
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.
-
B.
Italian military position
An Italian military position is a specific role or rank within Italy's armed forces hierarchy, defining an individual's responsibilities, authority, and duties in military operations and organization.
-
C.
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.
-
D.
Italian Army cavalry regiment
An Italian Army cavalry regiment is a military unit specializing in reconnaissance, security, and mobile combat operations, historically mounted on horses and now equipped with armored vehicles and modern weaponry.
-
E.
Italo-Spanish military unit
An Italo-Spanish military unit is a combined armed force formation composed of Italian and Spanish personnel, resources, and command structures, organized to conduct joint military operations.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:32 p.m.