Triple
T23819695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Army regimental system |
E589196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army unit system |
C21590
|
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: United States Army unit system Context triple: [United States Army regimental system, instanceOf, United States Army unit system]
-
A.
U.S. Army organizational element
A U.S. Army organizational element is a structured unit of soldiers, equipment, and command relationships designed to perform specific missions within the Army’s overall force hierarchy.
-
B.
U.S. Army regiment
chosen
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.
-
C.
U.S. Army battalion
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.
-
D.
United States Army field army
A United States Army field army is a large, operational-level formation typically composed of multiple corps, organized to conduct sustained, large-scale land combat operations within a theater of war.
-
E.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 7:59 p.m.