Triple
T10725026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 78th Aviation Troop Command |
E252918
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Georgia Army National Guard 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: Georgia Army National Guard unit Context triple: [78th Aviation Troop Command, instanceOf, Georgia Army National Guard unit]
-
A.
Confederate States Army unit
A Confederate States Army unit is an organized military formation, such as a regiment, battalion, or company, that served under the Confederate States of America during the American Civil War.
-
B.
branch of the Confederate States Army
A branch of the Confederate States Army is a major functional subdivision, such as infantry, cavalry, or artillery, responsible for a specific type of military operation within the Confederate land forces during the American Civil War.
-
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 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.
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.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:14 p.m.