Triple
T23627567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | air defence command |
E583510
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military organizational function |
C47033
|
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 organizational function Context triple: [air defence command, instanceOf, military organizational function]
-
A.
military operational function
chosen
A military operational function is a fundamental category of related tasks and capabilities that collectively enable armed forces to plan, conduct, and sustain operations to achieve strategic and tactical objectives.
-
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.
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.
-
D.
military organizational doctrine
Military organizational doctrine is the formalized set of principles, structures, and procedures that guide how armed forces are organized, coordinated, and employed to achieve strategic and operational objectives.
-
E.
military government function
A military government function is an activity or responsibility carried out by armed forces to administer, control, or support governance and public order, especially in times of conflict, occupation, or emergency.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:46 p.m.