Triple
T37506210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States House Select Committee on the January 6 Attack |
E932097
|
entity |
| Predicate | notableHearing |
—
|
GENERATED |
| Object | June 9, 2022 prime-time hearing on January 6 attack |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHearing Context triple: [United States House Select Committee on the January 6 Attack, notableHearing, June 9, 2022 prime-time hearing on January 6 attack]
-
A.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
B.
heldPublicHearings
Indicates that formal meetings open to the public were conducted to gather input, discuss issues, or present information.
-
C.
hearingSchedule
chosen
Indicates that a formal hearing or legal proceeding is scheduled to occur at a specified time and/or place.
-
D.
notableMeeting
Indicates that two or more entities participated together in a meeting considered significant or noteworthy in some context.
-
E.
notableCourt
Indicates that a particular court is especially significant or noteworthy in relation to the subject.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.