Triple
T29460123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Héroe de la República de Cuba |
E747212
|
entity |
| Predicate | isHighestHonoraryTitleOf |
P18549
|
FINISHED |
| Object | Cuba |
—
|
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: Cuba | Statement: [Héroe de la República de Cuba, isHighestHonoraryTitleOf, Cuba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighestHonoraryTitleOf Context triple: [Héroe de la República de Cuba, isHighestHonoraryTitleOf, Cuba]
-
A.
isHighestRoyalTitleIn
Indicates that a royal title is the most senior or supreme title within a specified realm, hierarchy, or political entity.
-
B.
honoraryTitleGrantedTo
Indicates that an honorary title has been formally conferred upon a particular entity.
-
C.
hasHonoraryTitle
Indicates that an entity has been granted a formal honorary title or distinction, typically in recognition of merit or achievement.
-
D.
isOneOfHighestHonoursOf
chosen
Indicates that something ranks among the most prestigious or esteemed honors within a particular field, context, or system.
-
E.
isHighestCeremonialRankIn
Indicates that an entity holds the top ceremonial position or title within a specified group, organization, or jurisdiction.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 3:49 p.m.