Triple
T37916975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knapp Commission investigations |
E945845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government commission inquiry |
C40706
|
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: government commission inquiry Context triple: [Knapp Commission investigations, instanceOf, government commission inquiry]
-
A.
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.
-
B.
government committee
A government committee is a formally established group of officials or representatives tasked with studying specific issues, developing recommendations, and overseeing particular areas of public policy or administration.
-
C.
official investigation
chosen
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.
-
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.
federal investigation
A federal investigation is a formal inquiry conducted by national government agencies to gather evidence, determine whether federal laws have been violated, and support potential enforcement or prosecution actions.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.