Triple
T208163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Army Training and Doctrine Command |
E4653
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army command |
C1992
|
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 command Context triple: [U.S. Army Training and Doctrine Command, instanceOf, United States Army command]
-
A.
branch of the United States Army
A branch of the United States Army is a specialized functional category, such as Infantry or Signal Corps, that organizes soldiers, training, and equipment around a distinct mission set and expertise area within the Army.
-
B.
branch of the United States Armed Forces
A branch of the United States Armed Forces is a distinct military service component (such as the Army, Navy, Air Force, Marine Corps, Space Force, or Coast Guard) with its own mission, structure, and responsibilities for national defense and security.
-
C.
United States Army installation
A United States Army installation is a designated military facility, base, or post that supports the housing, training, operations, logistics, and administration of Army personnel and equipment.
-
D.
U.S. Army doctrine
U.S. Army doctrine is the authoritative, evolving body of fundamental principles, tactics, techniques, and procedures that guides how the Army organizes, trains, and conducts operations across the range of military activities.
-
E.
land warfare service branch
A land warfare service branch is a military organization primarily responsible for conducting combat and support operations on land using ground forces and associated assets.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.