Triple
T10175673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilda Beatriz Guevara |
E235843
|
entity |
| Predicate | publicStanceOnFather |
P92535
|
FINISHED |
| Object | defends Che Guevara’s legacy |
—
|
LITERAL FINISHED |
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: defends Che Guevara’s legacy | Statement: [Hilda Beatriz Guevara, publicStanceOnFather, defends Che Guevara’s legacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicStanceOnFather Context triple: [Hilda Beatriz Guevara, publicStanceOnFather, defends Che Guevara’s legacy]
-
A.
relationshipWithFather
Indicates a familial relationship that specifically connects an individual to their father.
-
B.
viewOfFather
Indicates that one entity is a visual representation, depiction, or perspective specifically of a father.
-
C.
fatherWas
Indicates that one entity was the male parent (father) of another entity in the past.
-
D.
fatherPosition
Indicates the spatial or positional relationship occupied by a father relative to another referenced entity or location.
-
E.
claimedFather
Indicates that one entity is asserted or alleged to be the father of another entity, without guaranteeing the claim’s truth.
- F. None of above. chosen
Provenance (4 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdecd3a2688190bce277bffffcbf8b |
completed | April 2, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69cd7edc6cf081909d95859d880a4059 |
completed | April 1, 2026, 8:23 p.m. |
Created at: March 30, 2026, 9:11 p.m.