Triple
T735041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States politics |
E14910
|
entity |
| Predicate | dominantPartySystem |
P19538
|
FINISHED |
| Object | two-party system |
—
|
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: two-party system | Statement: [United States politics, dominantPartySystem, two-party system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantPartySystem Context triple: [United States politics, dominantPartySystem, two-party system]
-
A.
dominantParty
Indicates that one party in a relationship holds primary control, authority, or influence over the other.
-
B.
otherMajorParty
Indicates that an entity is affiliated with a major political party other than a specified primary or reference party.
-
C.
politicalParty
Indicates that an entity is affiliated with, belongs to, or is a member of a specific political party.
-
D.
historicalDominantParties
Indicates that certain political parties have historically held dominant or ruling positions within a given political system or jurisdiction.
-
E.
politicalPartyOfGovernment
Indicates that a specified political party is the one currently forming or leading the government of a given jurisdiction.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fafee081909bf356854c09aaff |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a66658948190bdae6e521951954f |
completed | March 1, 2026, 8:49 p.m. |
Created at: March 1, 2026, 7:37 p.m.