Triple
T28816208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solid South |
E727645
|
entity |
| Predicate | supportedPartyInPresidentialElections |
P203793
|
FINISHED |
| Object | Democratic Party |
E125
|
NE 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: Democratic Party | Statement: [Solid South, supportedPartyInPresidentialElections, Democratic Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedPartyInPresidentialElections Context triple: [Solid South, supportedPartyInPresidentialElections, Democratic Party]
-
A.
partyOfElectedPresident
Indicates the political party to which an elected president belongs.
-
B.
supportedCandidateInElection
Indicates that one entity endorsed or backed another entity as a candidate in a specific election.
-
C.
supportPartyLeader
Indicates that one entity backs, endorses, or actively helps a political party leader in their role or objectives.
-
D.
eligibleParties
Indicates that certain entities are qualified or permitted to participate in, benefit from, or be subject to a specified agreement, process, or condition.
-
E.
partyInElection
Indicates that a political party participates as a contestant or actor in a specific election.
- F. None of above. chosen
Provenance (5 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a0205c0bff481908238a382459b3a93 |
completed | May 11, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24d3edf134819095a8da1cd7781edb |
completed | June 7, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a0205143f20819087ee31576835be26 |
completed | May 11, 2026, 4:34 p.m. |
| PDg | Predicate description generation | batch_6a0205bfab208190982728a690ce183d |
completed | May 11, 2026, 4:37 p.m. |
Created at: April 28, 2026, 6:32 a.m.