Triple
T26778828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article II: Obstruction of Congress |
E670192
|
entity |
| Predicate | impeachmentArticleNumber |
P161959
|
FINISHED |
| Object | II |
—
|
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: II | Statement: [Article II: Obstruction of Congress, impeachmentArticleNumber, II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impeachmentArticleNumber Context triple: [Article II: Obstruction of Congress, impeachmentArticleNumber, II]
-
A.
numberOfArticlesOfImpeachment
Indicates the specific count of formal impeachment charges brought against a person or officeholder.
-
B.
impeachmentInitiation
Indicates the formal start of a process to charge and potentially remove a public official from office for alleged misconduct.
-
C.
impeachmentYear
Indicates the year in which an entity (typically a public official) was formally impeached.
-
D.
subjectToImpeachmentVote
Indicates that a person or official is currently facing or has been formally brought to a legislative vote on whether to impeach them.
-
E.
impeachedIn
Indicates that a person has been formally charged with misconduct through an impeachment process in a specified jurisdiction or legislative body.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 4:07 a.m.