Triple
T60889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roe v. Wade |
E1209
|
entity |
| Predicate | hasVoteSplit |
P4510
|
FINISHED |
| Object | 7–2 |
—
|
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: 7–2 | Statement: [Roe v. Wade, hasVoteSplit, 7–2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVoteSplit Context triple: [Roe v. Wade, hasVoteSplit, 7–2]
-
A.
hasElectionFraction
Indicates that a specified portion or fraction of the total vote or electorate is associated with a particular election-related entity or outcome.
-
B.
voteCountedIn
Indicates that a particular vote has been included in the official tally for a specific election, contest, or jurisdiction.
-
C.
hasElectoralVotes
Indicates that a political entity (such as a state or district) possesses a specified number of votes in an electoral system used to choose an officeholder.
-
D.
canVoteOn
Indicates that an entity has the right or permission to participate in a decision-making process by casting a vote on a specific item, issue, or proposal.
-
E.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a251a1b8ac8190b44be4c3c41e5681 |
completed | Feb. 28, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69a24ea0bec48190b2af1fb287e9e692 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a251a088f8819083797c2baf310c39 |
completed | Feb. 28, 2026, 2:23 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.