Triple
T25032432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Carolina Democratic Party |
E626883
|
entity |
| Predicate | twoPartySystemMember |
P157565
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [South Carolina Democratic Party, twoPartySystemMember, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: twoPartySystemMember Context triple: [South Carolina Democratic Party, twoPartySystemMember, Yes]
-
A.
partnerInPolitics
Indicates that two entities are political partners, collaborating or aligned in political activities, campaigns, or governance.
-
B.
constituentParty
Indicates that an entity is a member or component party within a larger party, group, or organizational structure.
-
C.
subjectPoliticalParty
Indicates the political party with which the subject is formally affiliated or identified.
-
D.
notableMemberParty
Indicates that a political party has a member who is particularly notable or prominent within that party.
-
E.
representedPoliticalEntity
Indicates that one entity has served as an official political representative or agent acting on behalf of another political entity.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44f70b1648190ab00365f89262d73 |
completed | May 1, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:07 a.m.