Triple
T17562351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkansas Republican Party |
E427722
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Republican Party affiliate |
C108
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Republican Party affiliate Context triple: [Arkansas Republican Party, instanceOf, Republican Party affiliate]
-
A.
Republican Party politician
chosen
A Republican Party politician is an elected or aspiring public official in the United States who is affiliated with the Republican Party and advocates for its political platform and policy priorities.
-
B.
Republican Party document
A Republican Party document is any written, printed, or digital material officially produced, endorsed, or distributed by the Republican Party to communicate its policies, positions, activities, or organizational information.
-
C.
Federalist Party politician
A Federalist Party politician is a public officeholder or candidate in the early United States who aligned with and promoted the Federalist Party’s platform favoring a strong central government, commercial interests, and closer ties with Britain.
-
D.
republican
A republican is an individual who supports or is associated with a political ideology or party that emphasizes representative government, limited central authority, and often conservative or right-leaning policies.
-
E.
republican branch of a ruling party
A republican branch of a ruling party is the organizational segment that promotes, manages, and implements the party’s republican ideology and policies within a political system.
- F. None of above.
Provenance (1 batch)
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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.