Triple
T7374905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Report of the Select Committee on Assassinations of the U.S. House of Representatives |
E170099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | congressional 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 report Context triple: [Final Report of the Select Committee on Assassinations of the U.S. House of Representatives, instanceOf, congressional report]
-
A.
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.
-
B.
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.
-
C.
parliamentary paper
A parliamentary paper is an official document produced or presented to a legislature, typically containing reports, proposals, evidence, or records used to inform and support parliamentary debate and decision-making.
-
D.
parliamentary record
A parliamentary record is an official, authoritative written or transcribed account of the proceedings, debates, decisions, and votes that occur within a parliamentary body.
-
E.
Act of Congress
An Act of Congress is a formal law or statute enacted by the United States Congress and, typically upon receiving the President’s signature or a veto override, becomes legally binding federal legislation.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:07 p.m.