Triple
T18472289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juventud Peronista |
E451331
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Peronist organization |
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: Peronist organization Context triple: [Juventud Peronista, instanceOf, Peronist organization]
-
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.
organización marxista
Una organización marxista es una entidad política o social estructurada en torno a la teoría marxista, que busca transformar las relaciones de producción capitalistas mediante la acción colectiva y la lucha de clases hacia una sociedad socialista o comunista.
-
C.
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.
-
D.
political organization
A political organization is a structured group of individuals who collectively pursue specific political goals, such as influencing public policy, gaining or maintaining power, or representing particular interests within a political system.
-
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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:34 a.m.