Triple
T2190885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew Jackson presidential election |
E49857
|
entity |
| Predicate | hasElectionDay |
P9219
|
FINISHED |
| Object | 1828-10-31 |
—
|
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: 1828-10-31 | Statement: [Andrew Jackson presidential election, hasElectionDay, 1828-10-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectionDay Context triple: [Andrew Jackson presidential election, hasElectionDay, 1828-10-31]
-
A.
hasElectionsFor
Indicates that a governing body, jurisdiction, or organization conducts elections to select or appoint members to a specified office, role, or representative body.
-
B.
hasRegularElections
Indicates that a governing body or political entity holds elections at consistent, scheduled intervals according to established rules or norms.
-
C.
hasElectionType
Indicates the specific category or kind of election associated with a given electoral event or process.
-
D.
electionHeldIn
Indicates that an election event took place within a specific geographic or political location.
-
E.
electionDate
chosen
Indicates the specific calendar date on which an election is scheduled to be or was held.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.