Triple
T30251430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Republican Congressional Committee |
E769211
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Republican Party organization |
C21981
|
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 organization Context triple: [National Republican Congressional Committee, instanceOf, Republican Party organization]
-
A.
Republican Party factional organization
A Republican Party factional organization is a structured group within the Republican Party that coordinates like-minded members and resources to influence party platforms, candidate selection, and policy priorities.
-
B.
Republican Party politician
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.
-
C.
conservative organization
chosen
A conservative organization is a structured group that promotes and advances right-leaning or traditional political, social, or economic values through advocacy, policy influence, and public engagement.
-
D.
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.
-
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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:40 p.m.