Triple
T21507997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reports on the relation of accounting standards to corporate regulation |
E530644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governmental investigative report |
C2
|
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: governmental investigative report Context triple: [Reports on the relation of accounting standards to corporate regulation, instanceOf, governmental investigative report]
-
A.
government report
chosen
A government report is an official document produced by a public agency that presents findings, data, analyses, or recommendations on matters of public policy, administration, or societal concern.
-
B.
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.
-
C.
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.
-
D.
institutional report
An institutional report is a formal document that presents structured information, analysis, and findings about an organization’s activities, performance, or compliance to internal or external stakeholders.
-
E.
policy report
A policy report is a structured document that analyzes a specific issue, evaluates options, and presents evidence-based recommendations to guide decision-making by policymakers or stakeholders.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:24 p.m.