Triple
T32927853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Act 1881 |
E842319
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military law |
C2025
|
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 Context triple: [Army Act 1881, instanceOf, British military law]
-
A.
military legal code
A military legal code is a formal system of laws and regulations that governs the conduct, discipline, rights, and obligations of members of the armed forces.
-
B.
United Kingdom Defence Regulation
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.
-
C.
military justice code
chosen
A military justice code is a formal set of laws and regulations that governs the conduct, discipline, and legal procedures applicable to members of the armed forces.
-
D.
military justice authority
A military justice authority is an official body or position within the armed forces responsible for administering, overseeing, and enforcing laws, regulations, and disciplinary procedures applicable to military personnel.
-
E.
British colonial law
British colonial law refers to the legal systems, statutes, and judicial practices imposed by Britain on its colonies, designed to maintain imperial control while selectively incorporating or reshaping local customs and institutions.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:20 a.m.