Triple
T8356223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1856 United States presidential election |
E196686
|
entity |
| Predicate | thirdPlacePopularVoteShare |
P29081
|
FINISHED |
| Object | 21.6% |
—
|
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: 21.6% | Statement: [1856 United States presidential election, thirdPlacePopularVoteShare, 21.6%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdPlacePopularVoteShare Context triple: [1856 United States presidential election, thirdPlacePopularVoteShare, 21.6%]
-
A.
popularVotesReceivedByThirdPlace
Indicates the number of popular votes obtained by the candidate or option that finished in third place in an election or contest.
-
B.
thirdPlaceRank
Indicates that an entity holds the third position in a ranking or ordered list relative to others.
-
C.
popularVoteShareThird
chosen
Indicates the proportion of total popular votes received by the third-place candidate or option in an election.
-
D.
thirdPlaceParty
Indicates that an entity finished in third place in a competitive event or ranking.
-
E.
thirdPlacePartyAbbreviation
Indicates the abbreviated name of a third-place political party associated with an entity or event.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804a344c819089c0a13fe66e3088 |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.