Triple

T8147770
Position Surface form Disambiguated ID Type / Status
Subject Estadio Banorte E190256 entity
Predicate hasHomeClubLeague P44115 FINISHED
Object Mexican football league system 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: Mexican football league system | Statement: [Estadio Banorte, hasHomeClubLeague, Mexican football league system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHomeClubLeague
Context triple: [Estadio Banorte, hasHomeClubLeague, Mexican football league system]
  • A. hasHomeClub
    Indicates that an entity (typically a person, such as an athlete) is associated with a particular club as their primary or official home organization.
  • B. hasHomeCountryLeague chosen
    Indicates that an entity (typically a sports team or player) is associated with a specific league that operates in its home country.
  • C. homeLeague
    Indicates that a sports team primarily competes in, or is officially associated with, a particular league as its main organizational affiliation.
  • D. hostLeague
    Indicates that one entity serves as the organizing league or governing competition framework for another entity, such as a team or event.
  • E. hasClub
    Indicates that an entity is associated with or belongs to a particular club.
  • 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_69ca82be7ba8819087de0147e9292c83 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb447e74e081908df774edb2134209 completed March 31, 2026, 3:50 a.m.
PD Predicate disambiguation batch_69cb36a0847c8190af9038aef78319b3 completed March 31, 2026, 2:51 a.m.
Created at: March 30, 2026, 5:36 p.m.