Triple

T8053810
Position Surface form Disambiguated ID Type / Status
Subject Mexican football league system E187741 entity
Predicate includesLiguillaFormat P67589 FINISHED
Object yes 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: yes | Statement: [Mexican football league system, includesLiguillaFormat, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesLiguillaFormat
Context triple: [Mexican football league system, includesLiguillaFormat, yes]
  • A. playsInAperturaAndClausuraFormat
    Indicates that a team or player participates in a competition structured with both Apertura (opening) and Clausura (closing) tournament phases.
  • B. includesLeague
    Indicates that an entity (such as a competition, organization, or system) contains or encompasses a specific league as one of its components.
  • C. includesCompetition
    Indicates that one entity contains, features, or encompasses a competition as part of its scope or content.
  • D. hasPlayOffsFor chosen
    Indicates that an entity organizes or includes playoff competitions specifically for another entity (such as a league, season, or division).
  • E. eligibleLeague
    Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
  • 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_69ca82b15e948190a62fd7af5218426a completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3f9fb8dc8190bacc1f66ddfd1cbf completed March 31, 2026, 3:29 a.m.
PD Predicate disambiguation batch_69cb049a1b9c8190811c396421ebf9c9 completed March 30, 2026, 11:17 p.m.
Created at: March 30, 2026, 5:25 p.m.