Triple
T9335722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Inquiry report |
E224637
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | congressional investigation 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: congressional investigation report Context triple: [Joint Inquiry report, instanceOf, congressional investigation 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.
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.
-
C.
United States congressional hearing
A United States congressional hearing is a formal meeting held by a committee or subcommittee of Congress to gather information, question witnesses, and create a public record on proposed legislation, government operations, or issues of national concern.
-
D.
section of the Congressional Record
A section of the Congressional Record is a distinct, thematically or procedurally organized portion of the official published account of the proceedings and debates of the United States Congress.
-
E.
human rights investigation report
A human rights investigation report is a structured document that presents findings, evidence, and analysis regarding alleged human rights violations, along with conclusions and recommendations for accountability and remedy.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:40 p.m.