Triple
T8423162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1955 bombing of Plaza de Mayo |
E198911
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Argentine history |
C14499
|
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: event in Argentine history Context triple: [1955 bombing of Plaza de Mayo, instanceOf, event in Argentine history]
-
A.
event in the history of Argentina
chosen
An event in the history of Argentina is a significant occurrence or development, situated in time and place, that has influenced the nation’s political, social, economic, or cultural trajectory.
-
B.
event in the history of Paraguay
An event in the history of Paraguay is a significant occurrence or development, situated in time and place, that has influenced the political, social, economic, or cultural trajectory of Paraguay.
-
C.
event in the history of Uruguay
An event in the history of Uruguay is any significant occurrence or development, political, social, cultural, or economic, that has notably influenced the country’s historical trajectory.
-
D.
event in the history of Bolivia
An event in the history of Bolivia is a significant occurrence or development, such as a political change, social movement, conflict, or cultural milestone, that has notably influenced the country's historical trajectory.
-
E.
event in the history of Brazil
An event in the history of Brazil is a significant occurrence or development—political, social, economic, cultural, or environmental—that has notably influenced the country’s trajectory over time.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:06 p.m.