Triple
T18455864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radical Civic Union |
E450901
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Argentine political party |
C23557
|
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: Argentine political party Context triple: [Radical Civic Union, instanceOf, Argentine political party]
-
A.
Argentine organization
chosen
An Argentine organization is any formally or informally structured group based in Argentina that coordinates people and resources to pursue shared goals, such as business, social, cultural, or political objectives.
-
B.
Peruvian political party
A Peruvian political party is an organized group of individuals in Peru that shares a common political ideology or agenda and seeks to gain and exercise governmental power through participation in elections and public policy-making.
-
C.
Ecuadorian political party
An Ecuadorian political party is an organized group within Ecuador that seeks to influence or control government by nominating candidates, contesting elections, and promoting specific ideological, social, or economic agendas.
-
D.
Hungarian political party
A Hungarian political party is an organized group within Hungary that seeks to influence or control government policy and leadership by contesting elections and representing specific ideological, social, or economic interests.
-
E.
Uruguayan politician
A Uruguayan politician is a public figure from Uruguay who engages in political activities, holds or seeks governmental office, and participates in shaping national or local public policy.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:31 a.m.