Triple
T26631967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Centauro Armored Division |
E668521
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Italian Army unit |
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: Royal Italian Army unit Context triple: [Italian Centauro Armored Division, instanceOf, Royal Italian Army unit]
-
A.
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.
-
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.
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.
-
D.
Italian light infantry corps
An Italian light infantry corps is a military formation composed of highly mobile, lightly equipped Italian soldiers trained for rapid maneuver, skirmishing, and operations in difficult terrain.
-
E.
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.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:25 a.m.