Triple
T19225803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congreso de 1816 |
E480734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Argentine political institution |
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 institution Context triple: [Congreso de 1816, instanceOf, Argentine political institution]
-
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.
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.
-
C.
department of Argentina
A department of Argentina is an administrative subdivision within a province, functioning as an intermediate level of government that groups together several municipalities or localities.
-
D.
Peronist politician
A Peronist politician is a political figure in Argentina who aligns with the populist, nationalist, and social-justice-oriented principles derived from the legacy of Juan and Eva Perón, typically emphasizing strong state intervention, labor rights, and charismatic leadership.
-
E.
Basque political institution
A Basque political institution is an organization or governing body that exercises political authority, representation, or administrative functions within the Basque Country’s unique multi-level system of autonomy and self-government.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:24 p.m.