Triple
T6325530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.J.Res.114 |
E141852
|
entity |
| Predicate | senateVoteType |
P24498
|
FINISHED |
| Object | Roll call vote |
—
|
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: Roll call vote | Statement: [H.J.Res.114, senateVoteType, Roll call vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: senateVoteType Context triple: [H.J.Res.114, senateVoteType, Roll call vote]
-
A.
voteType
chosen
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
B.
senateVoteTallyFor
Indicates the recorded vote count or outcome in the senate for a particular measure, motion, or item.
-
C.
ratificationVote
Indicates a formal vote taken to approve, confirm, or give official sanction to a decision, agreement, or action.
-
D.
vetoType
Indicates the specific kind or category of veto applied in a decision-making or approval process.
-
E.
votePattern
Indicates a recurring way or tendency in how an entity casts votes across issues, candidates, or time.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e701ec81908e5eaa0660d01a4b |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.