Triple
T16124275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 212th Armored Field Artillery Battalion |
E391225
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army artillery battalion |
C22556
|
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: U.S. Army artillery battalion Context triple: [212th Armored Field Artillery Battalion, instanceOf, U.S. Army artillery battalion]
-
A.
U.S. Army battalion
chosen
A U.S. Army battalion is a mid-sized tactical unit, typically consisting of 300–1,000 soldiers organized into several companies, capable of independent operations under a battalion commander.
-
B.
artillery unit
An artillery unit is a military formation equipped with long-range weapons designed to deliver indirect fire support against enemy targets from protected or distant positions.
-
C.
artillery battery
An artillery battery is a military unit composed of multiple artillery pieces, their crews, and supporting equipment, organized to deliver coordinated indirect fire on designated targets.
-
D.
U.S. Army aviation battalion
A U.S. Army aviation battalion is a military unit that organizes, operates, and sustains multiple helicopter or fixed-wing aircraft companies to provide air assault, reconnaissance, transport, medical evacuation, and support capabilities to ground forces.
-
E.
U.S. Army regiment
A U.S. Army regiment is a traditional military unit designation that historically grouped multiple battalions or companies under a common lineage and identity, now used primarily for organizational, administrative, and ceremonial purposes rather than as a primary tactical formation.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5 a.m.