Triple
T25572083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd U.S. Cavalry |
E641001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Regular Army unit |
C2497
|
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: Regular Army unit Context triple: [2nd U.S. Cavalry, instanceOf, Regular Army unit]
-
A.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
B.
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.
-
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.
U.S. Army infantry division
A U.S. Army infantry division is a large, combined-arms military formation, typically consisting of several brigades and supporting units, organized and equipped primarily for ground combat operations centered on infantry forces.
-
E.
U.S. Army National Guard division
A U.S. Army National Guard division is a large, state-based military formation that can be federally mobilized, combining multiple brigades and support units to conduct sustained combat and support operations alongside active-duty Army forces.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 3:58 p.m.