Triple
T31406348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Warrant of 14 June 1945 |
E801139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military law measure |
C40173
|
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: British military law measure Context triple: [Royal Warrant of 14 June 1945, instanceOf, British military law measure]
-
A.
United Kingdom Defence Regulation
chosen
United Kingdom Defence Regulation is a conceptual class representing the body of legal rules, statutory instruments, and administrative measures enacted by the UK government to organize, control, and direct national defence activities, including military operations, security protocols, and wartime emergency powers.
-
B.
British Army order
A British Army order is an official directive issued by a competent military authority within the British Army that prescribes specific actions, procedures, or policies to be followed by subordinate personnel.
-
C.
British Army doctrine publication
A British Army doctrine publication is an official document that articulates the Army’s authoritative principles, concepts, and guidance for the conduct of operations and training.
-
D.
United Kingdom military position
A United Kingdom military position is a specific role or rank within the British Armed Forces, defined by its responsibilities, authority, and place in the military hierarchy.
-
E.
British Army deployment
British Army deployment is the organized assignment and movement of British Army personnel and resources to specific locations or operations to fulfill military objectives and commitments.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 8:32 p.m.