Triple
T37506212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States House Select Committee on the January 6 Attack |
E932097
|
entity |
| Predicate | issuedFinalReport |
P188173
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [United States House Select Committee on the January 6 Attack, issuedFinalReport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuedFinalReport Context triple: [United States House Select Committee on the January 6 Attack, issuedFinalReport, true]
-
A.
finalReportType
Indicates the specific category or format assigned to a report when it is in its final, completed state.
-
B.
reportsOutcomeOf
Indicates that one entity communicates or provides the result, consequence, or final status of another entity’s process, event, or action.
-
C.
issuedDocument
Indicates that one entity has formally created and provided an official document to another entity.
-
D.
issuedWork
Indicates that an entity has formally produced, published, or released a particular work.
-
E.
finalReportSubject
Indicates that an entity serves as the main topic or focus of a final report.
- F. None of above. chosen
Provenance (4 batches)
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. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.