Triple
T32292002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodhead Commission |
E824987
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal commission of inquiry |
C60079
|
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: royal commission of inquiry Context triple: [Woodhead Commission, instanceOf, royal commission of inquiry]
-
A.
Royal commission
chosen
A royal commission is a formal public inquiry established by a monarch or government to investigate and report on a specific issue of significant public concern, often with broad powers to collect evidence and make recommendations.
-
B.
South African commission of inquiry
A South African commission of inquiry is an ad hoc, government-appointed body tasked with independently investigating and reporting on specific matters of public concern, often with powers to summon witnesses and gather evidence.
-
C.
borough commission
A borough commission is a local governing body or administrative board responsible for overseeing municipal functions, services, and regulations within a specific borough.
-
D.
British imperial inquiry
A British imperial inquiry is a formal investigation commissioned by the British Empire or its government to examine events, policies, or conditions in colonial territories, often to manage crises, legitimize authority, or recommend administrative reforms.
-
E.
military inquiry board
A military inquiry board is a formal panel of military officers convened to investigate specific incidents, actions, or conduct within the armed forces and to determine facts, responsibility, and potential recommendations.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:44 a.m.