Triple
T17139723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | second impeachment of Donald Trump |
E415931
|
entity |
| Predicate | votingResultHouseYesVotes |
P91234
|
FINISHED |
| Object | 232 |
—
|
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: 232 | Statement: [second impeachment of Donald Trump, votingResultHouseYesVotes, 232]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingResultHouseYesVotes Context triple: [second impeachment of Donald Trump, votingResultHouseYesVotes, 232]
-
A.
yesVotes
Indicates that a specified entity has cast or received affirmative votes in a decision-making or voting context.
-
B.
passedHouseVote
Indicates that a proposed measure or bill has received sufficient affirmative votes to be approved by the House of Representatives.
-
C.
senateVoteTallyFor
Indicates the recorded vote count or outcome in the senate for a particular measure, motion, or item.
-
D.
numberOfSupportVotesInChamber
chosen
Indicates the count of votes cast in favor of a proposal within a specific legislative chamber.
-
E.
voteResult
Indicates the outcome or decision produced by a voting process involving the related entities.
- F. None of above.
Provenance (3 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d318a88190aae8d776376c8053 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.