Triple

T30653707
Position Surface form Disambiguated ID Type / Status
Subject Homenaje a Dos Leyendas E780328 entity
Predicate honoreeType P43861 FINISHED
Object wrestling promoter 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: wrestling promoter | Statement: [Homenaje a Dos Leyendas, honoreeType, wrestling promoter]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: honoreeType
Context triple: [Homenaje a Dos Leyendas, honoreeType, wrestling promoter]
  • A. honoreeRole chosen
    Indicates the specific role, title, or capacity in which an individual is being honored in relation to an award, event, or recognition.
  • B. honoreeField
    Indicates that one entity is recognized or designated as the honoree associated with another entity, such as an award, event, or dedication.
  • C. honoredPerson
    Indicates that a person is the recipient of honor, recognition, or special distinction from another party or in a particular context.
  • D. typicalHonoree
    Indicates that an entity is the usual or characteristic recipient of an honor, award, or recognition associated with another entity.
  • E. honoreeKnownFor
    Indicates that an honoree is recognized or celebrated specifically for a particular work, achievement, contribution, or notable attribute.
  • 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_69f224a5d2b481908a6853cd0138e2d7 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6e6029a10819098ff21f58079e70e completed May 3, 2026, 6:06 a.m.
PD Predicate disambiguation batch_69f6e3d5e8188190b1e1c2e5d1b77031 completed May 3, 2026, 5:57 a.m.
Created at: April 29, 2026, 8:30 p.m.