Triple
T26082416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Colson |
E657880
|
entity |
| Predicate | involvesPoliticalParty |
P99882
|
FINISHED |
| Object | Republican Party |
—
|
NE NERFINISHED |
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: Republican Party | Statement: [United States v. Colson, involvesPoliticalParty, Republican Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesPoliticalParty Context triple: [United States v. Colson, involvesPoliticalParty, Republican Party]
-
A.
subjectPoliticalParty
Indicates the political party with which the subject is formally affiliated or identified.
-
B.
affectedPoliticalParty
chosen
Indicates that a political party is impacted or influenced by a particular event, action, policy, or situation.
-
C.
partnerPoliticalAffiliation
Indicates that one entity has a political affiliation that is associated with, or shared by, its partner entity.
-
D.
participatesInPoliticsOf
Indicates involvement or active engagement by one entity in the political processes, affairs, or governance activities of another entity.
-
E.
politicalParty
Indicates that an entity is affiliated with, belongs to, or is a member of a specific political party.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 26, 2026, 7:39 p.m.