Triple
T20148028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | operations directorate |
E491358
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military staff branch |
C15294
|
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: military staff branch Context triple: [operations directorate, instanceOf, military staff branch]
-
A.
branch of service
A branch of service is a distinct organizational subdivision within a nation’s armed forces or public service, defined by its specific mission, capabilities, and operational domain.
-
B.
United States military staff organization
chosen
A United States military staff organization is a structured group of officers and enlisted personnel organized into functional sections (e.g., personnel, intelligence, operations, logistics) that support a commander in planning, coordinating, and executing missions.
-
C.
military administrative corps
A military administrative corps is a specialized branch of the armed forces responsible for managing personnel, logistics, finance, records, and other support functions that enable effective military operations.
-
D.
military medical branch
A military medical branch is the specialized division of a nation's armed forces responsible for providing healthcare, medical support, and emergency treatment to military personnel in both peacetime and combat operations.
-
E.
military administrative structure
A military administrative structure is the organized system of offices, roles, procedures, and chains of command that manage the planning, support, and governance of armed 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
Created at: April 11, 2026, 11:33 p.m.