Triple
T22893235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defence Act of Zimbabwe |
E568098
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | primary defence legislation |
C31991
|
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: primary defence legislation Context triple: [Defence Act of Zimbabwe, instanceOf, primary defence legislation]
-
A.
defence policy legislation
chosen
Defence policy legislation comprises the laws and regulations that govern a nation’s military organization, capabilities, operations, and strategic use of force in alignment with national security objectives and international obligations.
-
B.
national security law
National security law is the body of legal rules, principles, and processes that govern how a state protects its national defense, intelligence, and foreign relations while balancing civil liberties and constitutional limits.
-
C.
canonical legislation
Canonical legislation is the body of laws and regulations established by ecclesiastical authority to govern the doctrine, discipline, and administration of a religious institution, particularly within the Christian tradition.
-
D.
emergency legislation
Emergency legislation is a special category of law enacted rapidly, often with expedited procedures and temporary scope, to address urgent or unforeseen crises requiring immediate governmental action.
-
E.
defence service
Defence service is an organized provision of military and security capabilities by a state or authorized entity to protect its sovereignty, territory, population, and interests from external and internal threats.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:40 p.m.