Triple
T32820975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyons Inquiry into Local Government |
E839434
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | independent inquiry |
C944
|
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: independent inquiry Context triple: [Lyons Inquiry into Local Government, instanceOf, independent inquiry]
-
A.
official investigation
An official investigation is a formal, authorized inquiry conducted by a competent authority to gather facts, determine the truth, and assess responsibility regarding a specific incident, allegation, or issue.
-
B.
judicial investigation
A judicial investigation is a formal, legally authorized inquiry conducted by judicial authorities to gather, examine, and evaluate evidence in order to determine whether laws have been violated and if legal proceedings should follow.
-
C.
Royal commission
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.
-
D.
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.
-
E.
public inquiry
chosen
A public inquiry is a formal, independent investigation commissioned by a government or authority to examine matters of significant public concern, establish facts, and make recommendations for future action or policy.
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:15 a.m.