Triple
T14138011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Party System |
E350348
|
entity |
| Predicate | precededByElectoralChange |
P112955
|
FINISHED |
| Object | election of 1828 |
—
|
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: election of 1828 | Statement: [Second Party System, precededByElectoralChange, election of 1828]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByElectoralChange Context triple: [Second Party System, precededByElectoralChange, election of 1828]
-
A.
electionChange
Indicates a change in the outcome, status, or key parameters of an election between two points in time.
-
B.
previousElectorate
Indicates that one electorate served as the earlier or former electoral district associated with another electorate.
-
C.
changedElectoralSystem
Indicates that an entity has altered or replaced a previously existing electoral system with a different one.
-
D.
positionBeforeElection
Indicates that an entity held a particular position or office prior to a specified election.
-
E.
incumbentBeforeElection
Indicates that the subject was already holding the relevant office or position prior to the specified election.
- F. None of above. chosen
Provenance (4 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610fb86c81909eb26bf9c13696ca |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 12:38 a.m.