Triple

T30653705
Position Surface form Disambiguated ID Type / Status
Subject Homenaje a Dos Leyendas E780328 entity
Predicate hasMainVenueRole P201014 FINISHED
Object CMLL’s primary tribute show 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: CMLL’s primary tribute show | Statement: [Homenaje a Dos Leyendas, hasMainVenueRole, CMLL’s primary tribute show]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMainVenueRole
Context triple: [Homenaje a Dos Leyendas, hasMainVenueRole, CMLL’s primary tribute show]
  • A. hasVenueFor
    Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
  • B. hasVenueIn
    Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
  • C. hasPrincipalVenue
    Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
  • D. isCentralVenueOf
    Indicates that a venue serves as the primary or main location for a specified event, organization, or activity.
  • E. notableVenueRole
    Indicates that an entity holds or has held a significant functional role or position at a particular venue or location.
  • 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_69f224a5d2b481908a6853cd0138e2d7 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69ffc1550cb481908628e446d9b67f7b completed May 9, 2026, 11:20 p.m.
PD Predicate disambiguation batch_69ffc10a74708190ae90e2c378791f70 completed May 9, 2026, 11:19 p.m.
PDg Predicate description generation batch_69ffc15434c8819093aa3b33813613be completed May 9, 2026, 11:20 p.m.
Created at: April 29, 2026, 8:30 p.m.