Triple
T7636964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 101st Airborne Division |
E172902
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | light infantry division |
C3680
|
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: light infantry division Context triple: [101st Airborne Division, instanceOf, light infantry division]
-
A.
light infantry unit
A light infantry unit is a military formation composed of highly mobile, lightly equipped soldiers optimized for rapid maneuver, reconnaissance, and operations in difficult terrain rather than heavy direct-fire engagements.
-
B.
airborne infantry division
chosen
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.
-
C.
armored infantry division
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.
-
D.
airborne infantry brigade
An airborne infantry brigade is a highly mobile, light infantry formation trained and equipped to deploy rapidly by air, including parachute or air assault operations, to seize and hold key objectives behind or ahead of enemy lines.
-
E.
parachute infantry regiment
A parachute infantry regiment is a military unit composed of soldiers trained and equipped to deploy by parachute into combat zones to conduct airborne assault, seizure, and holding of 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:57 p.m.