Triple
T15601742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Sixth |
E375048
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army armored division |
C36396
|
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 armored division Context triple: [Super Sixth, instanceOf, U.S. Army armored division]
-
A.
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.
-
B.
U.S. Army infantry brigade
A U.S. Army infantry brigade is a modular, combined-arms combat unit typically consisting of several infantry battalions and supporting elements, organized to conduct sustained ground operations across a range of missions.
-
C.
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.
-
D.
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.
-
E.
armored regiment
An armored regiment is a military unit equipped primarily with tanks and other armored fighting vehicles, organized to conduct offensive and defensive ground combat operations.
- F. None of above. chosen
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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:12 a.m.