Triple
T31723706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golpe de Estado de 1955 en Argentina |
E809650
|
entity |
| Predicate | esRecordadoComo |
P67666
|
FINISHED |
| Object | Revolución Libertadora |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Revolución Libertadora | Statement: [Golpe de Estado de 1955 en Argentina, esRecordadoComo, Revolución Libertadora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: esRecordadoComo Context triple: [Golpe de Estado de 1955 en Argentina, esRecordadoComo, Revolución Libertadora]
-
A.
isRememberedAs
chosen
Indicates that an entity is recalled or regarded in a particular way in someone’s memory or collective remembrance.
-
B.
isRememberedOn
Indicates that an entity is commemorated, recalled, or honored on a specific date or occasion.
-
C.
rememberedFor
Indicates that one entity is known or recognized primarily because of, or in association with, another entity or achievement.
-
D.
rememberedThrough
Indicates that one entity is remembered, commemorated, or kept in memory by means of, or through the influence of, another entity or medium.
-
E.
isMemorizedFor
Indicates that something has been committed to memory specifically for a particular purpose, context, or entity.
- F. None of above.
Provenance (3 batches)
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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aafa2a1481909ecc84df0624c2b9 |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:19 p.m.