Triple
T16560352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Motor Rifle Division |
E402320
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mechanized infantry division |
C16076
|
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: mechanized infantry division Context triple: [1st Motor Rifle Division, instanceOf, mechanized infantry division]
-
A.
mechanized infantry battalion
A mechanized infantry battalion is a military unit composed of infantry soldiers equipped with armored vehicles that provide protected mobility, firepower, and support for rapid, combined-arms operations on the battlefield.
-
B.
armored infantry division
chosen
An armored infantry division is a large, combined-arms military formation that integrates mechanized infantry, tanks, artillery, and support units to conduct sustained offensive and defensive ground operations.
-
C.
U.S. Army armored division
A U.S. Army armored division is a large, combined-arms military formation centered on tanks and mechanized infantry, designed to conduct high-intensity, mobile ground combat operations.
-
D.
Wehrmacht infantry division
A Wehrmacht infantry division was a World War II-era German Army formation composed primarily of foot soldiers, supported by artillery, engineers, and logistical units, organized for sustained ground combat operations.
-
E.
airborne infantry division
An airborne infantry division is a large military formation of specially trained soldiers equipped and organized to deploy rapidly by air, typically via parachute or air assault, to seize and hold key objectives behind enemy lines.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:15 a.m.