Triple
T1264318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Bork |
E12566
|
entity |
| Predicate | senateVoteResult |
P10095
|
FINISHED |
| Object | U.S. Senate rejected nomination 58–42 |
—
|
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: U.S. Senate rejected nomination 58–42 | Statement: [Robert Bork, senateVoteResult, U.S. Senate rejected nomination 58–42]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: senateVoteResult Context triple: [Robert Bork, senateVoteResult, U.S. Senate rejected nomination 58–42]
-
A.
ratificationVote
Indicates a formal vote taken to approve, confirm, or give official sanction to a decision, agreement, or action.
-
B.
voteResult
chosen
Indicates the outcome or decision produced by a voting process involving the related entities.
-
C.
dateOfFinalSenateVotes
Indicates the calendar date on which the final voting session occurred in the Senate for a given measure or action.
-
D.
vetoedBy
Indicates that an action, decision, or proposal was rejected or blocked by a specific entity with veto authority.
-
E.
voteSplit
Indicates that a voting outcome is divided among multiple options or parties rather than being unanimous or clearly majority.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4c03573a48190b5851f0a734c2d6f |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bb7058e88190825b0cba5ee60b51 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.