Triple
T16700096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States House Select Committee hearings on the January 6 Attack |
E405821
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | congressional hearing series |
C8553
|
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 hearing series Context triple: [United States House Select Committee hearings on the January 6 Attack, instanceOf, congressional hearing series]
-
A.
United States congressional hearing
chosen
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.
-
B.
congressional debate
A congressional debate is a structured, formal discussion in which participants advocate for or against proposed legislation, simulating the procedures and rhetorical style of a legislative body.
-
C.
series of legislatures
A series of legislatures is a conceptual class representing a sequential collection of legislative bodies or assemblies that convene over successive terms or periods within a political system.
-
D.
congressional caucus
A congressional caucus is a group of members of the U.S. Congress who organize around shared interests, ideologies, or demographic characteristics to coordinate legislative strategies and policy goals.
-
E.
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.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:19 a.m.