Triple
T30213050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alberto Korda |
E768121
|
entity |
| Predicate | signatureWorkTitle |
P24259
|
FINISHED |
| Object | Guerrillero Heroico |
—
|
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: Guerrillero Heroico | Statement: [Alberto Korda, signatureWorkTitle, Guerrillero Heroico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureWorkTitle Context triple: [Alberto Korda, signatureWorkTitle, Guerrillero Heroico]
-
A.
workTitle
chosen
Indicates the formal title or name of a work (such as a book, artwork, or composition) associated with an entity.
-
B.
workTitleType
Indicates the specific category or type of a work’s title (e.g., main title, alternative title, translated title) in relation to that work.
-
C.
signatureWork
Indicates that the work is a defining or most representative creation associated with an entity (such as a person, group, or organization).
-
D.
signatureWorkType
Indicates the specific category or type of work that serves as a defining or primary example associated with an entity.
-
E.
titleOrRole
Indicates that one entity serves as the title, position, or role held or described by another 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 7:33 p.m.