Triple
T3345915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1852 United States presidential election |
E70373
|
entity |
| Predicate | percentageWinner |
P36641
|
FINISHED |
| Object | 50.8 |
—
|
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: 50.8 | Statement: [1852 United States presidential election, percentageWinner, 50.8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: percentageWinner Context triple: [1852 United States presidential election, percentageWinner, 50.8]
-
A.
winnerCount
Indicates the number of entities that are designated as winners in a given context or event.
-
B.
hasPopularVotePercentageForWinner
chosen
Indicates the percentage of the total popular vote received by the winning candidate or option in an election or vote.
-
C.
positionOfWinner
Indicates the relationship that identifies which entity holds the winning position or rank in a competition or contest.
-
D.
mainWinner
Indicates that one entity is the primary or overall winner in a competition, contest, or comparative outcome relative to others.
-
E.
popularVotePercentageLoser
Indicates the percentage of the total popular vote received by the candidate or party that did not win the election.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1f36c74819093ef2c74a46c2351 |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.