Triple
T33637371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States presidential election of 1820 |
E861732
|
entity |
| Predicate | formalVoteCountDateInCongress |
P108125
|
FINISHED |
| Object | 1821-02-14 |
—
|
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: 1821-02-14 | Statement: [United States presidential election of 1820, formalVoteCountDateInCongress, 1821-02-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalVoteCountDateInCongress Context triple: [United States presidential election of 1820, formalVoteCountDateInCongress, 1821-02-14]
-
A.
voteDate
Indicates the date on which a vote or voting action took place.
-
B.
electoralVoteCountingDate
chosen
Indicates the date on which electoral votes are formally counted or tallied in an election process.
-
C.
dateOfFinalSenateVotes
Indicates the calendar date on which the final voting session occurred in the Senate for a given measure or action.
-
D.
electoralCollegeVoteDate
Indicates the date on which Electoral College votes are formally cast for a given election.
-
E.
datePassedCongress
Indicates that a proposed measure or bill has successfully received approval from both chambers of a legislative congress.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:42 a.m.