Triple
T9386954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defence Digital |
E225927
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ministry of Defence organisation |
C5977
|
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: Ministry of Defence organisation Context triple: [Defence Digital, instanceOf, Ministry of Defence organisation]
-
A.
organisational unit of the UK Ministry of Defence
chosen
An organisational unit of the UK Ministry of Defence is a formally defined structural entity within the department, such as a command, agency, directorate, or division, responsible for specific defence-related functions, resources, and decision-making.
-
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.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
-
D.
military support organization
A military support organization is an entity that provides logistical, administrative, technical, and welfare services to enable and sustain the effective operation of armed forces.
-
E.
military political organ
A military political organ is an institutional body within the armed forces responsible for overseeing political education, ideological control, and party or state loyalty among military personnel.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:45 p.m.