Triple
T33389148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 12th United States presidential election |
E854997
|
entity |
| Predicate | electoralVotesForMainOpponent |
P9221
|
FINISHED |
| Object | 34 |
—
|
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: 34 | Statement: [12th United States presidential election, electoralVotesForMainOpponent, 34]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralVotesForMainOpponent Context triple: [12th United States presidential election, electoralVotesForMainOpponent, 34]
-
A.
opponentElectoralVotes
chosen
Indicates the number of electoral votes received by the opposing candidate or party in an election.
-
B.
voteShareMainOpponent
Indicates the proportion of total votes received by the primary opposing candidate or party in an election.
-
C.
electoralOpponents
Indicates that two or more parties or candidates are competing against each other in the same election.
-
D.
popularVoteOpponent
Indicates that one entity is the opponent of another in a popular vote or general election contest.
-
E.
popularVoteCountOpponent
Indicates the number of votes received by the opposing candidate or party in a popular vote contest.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 1, 2026, 1:35 a.m.