Triple
T28317226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defence Secretariat (South Africa) |
E717170
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civilian defence administration body |
C3213
|
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: civilian defence administration body Context triple: [Defence Secretariat (South Africa), instanceOf, civilian defence administration body]
-
A.
civilian administrative body
A civilian administrative body is a non-military organization responsible for managing public affairs, implementing policies, and providing governmental services within a defined jurisdiction.
-
B.
public administration body
chosen
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
C.
Ministry of Defence facility
A Ministry of Defence facility is a secured government-controlled site used for the planning, coordination, support, and execution of national defence and military operations.
-
D.
civil defence equipment
Civil defence equipment comprises tools, devices, and systems designed to protect civilians, support emergency response, and mitigate the impacts of disasters, conflicts, or other large-scale threats.
-
E.
defence establishment
A defence establishment is an organized institution or network of institutions responsible for planning, maintaining, and deploying a nation's military capabilities and security infrastructure.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 12:21 a.m.