Triple
T38263473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Board (for policing matters) |
E1017989
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | army governance body |
C21094
|
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: army governance body Context triple: [Army Board (for policing matters), instanceOf, army governance body]
-
A.
military decision-making body
chosen
A military decision-making body is an organized group of authorized personnel responsible for analyzing strategic and tactical information, evaluating options, and issuing binding directives that guide military operations and policy.
-
B.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
C.
army general staff
The army general staff is a centralized body of senior military officers responsible for planning, coordinating, and directing an army’s operations, strategy, logistics, and administration.
-
D.
air force governing body
The air force governing body is the central authority responsible for overseeing, directing, and regulating the organization, operations, policies, and strategic development of an air force.
-
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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.