Triple
T30440007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Army training and doctrine commands |
E774414
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italian Army organization |
C29988
|
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 Army organization Context triple: [Italian Army training and doctrine commands, instanceOf, Italian Army organization]
-
A.
Italian military organization
chosen
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 army corps
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.
-
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.
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.
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.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:08 p.m.