Triple
T5463494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General of the Armies (posthumous) |
E122649
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army rank |
C1739
|
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 rank Context triple: [General of the Armies (posthumous), instanceOf, United States Army rank]
-
A.
United States Army position
A United States Army position is a specific role or job within the Army’s organizational structure, defined by rank, responsibilities, and duties in support of military operations and administration.
-
B.
United States Army command
The United States Army command is the organizational structure and authority framework responsible for directing, coordinating, and controlling Army forces and operations to accomplish national defense objectives.
-
C.
military rank structure
chosen
A military rank structure is a hierarchical system that organizes service members into levels of authority and responsibility, defining command relationships, roles, and progression within the armed forces.
-
D.
U.S. Army qualification insignia
U.S. Army qualification insignia are badges worn by soldiers to signify their proficiency, training, and achievement in specific military skills or specialties.
-
E.
civilian office in the United States Department of the Army
A civilian office in the United States Department of the Army is an organizational unit staffed primarily by non-military personnel that supports the Army’s administrative, logistical, policy, or technical functions under the authority of the Department of the Army.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:08 p.m.