Triple
T1669195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brett M. Kavanaugh |
E36084
|
entity |
| Predicate | confirmationVoteResult |
P10095
|
FINISHED |
| Object | confirmed by the United States Senate |
—
|
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: confirmed by the United States Senate | Statement: [Brett M. Kavanaugh, confirmationVoteResult, confirmed by the United States Senate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmationVoteResult Context triple: [Brett M. Kavanaugh, confirmationVoteResult, confirmed by the United States Senate]
-
A.
voteResult
chosen
Indicates the outcome or decision produced by a voting process involving the related entities.
-
B.
voteCertificationBy
Indicates that a vote or election result has been formally certified or validated by a specified entity.
-
C.
voteCountedIn
Indicates that a particular vote has been included in the official tally for a specific election, contest, or jurisdiction.
-
D.
yesVotes
Indicates that a specified entity has cast or received affirmative votes in a decision-making or voting context.
-
E.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abc0e8d5648190915ff689c7ca42bc |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69a907d331748190963d4ab1a2741537 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.