Triple
T28025549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga MX Clausura |
E708111
|
entity |
| Predicate | numberOfChampionsPerSeason |
P66376
|
FINISHED |
| Object | 1 Clausura champion |
—
|
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: 1 Clausura champion | Statement: [Liga MX Clausura, numberOfChampionsPerSeason, 1 Clausura champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfChampionsPerSeason Context triple: [Liga MX Clausura, numberOfChampionsPerSeason, 1 Clausura champion]
-
A.
totalChampionsCount
Indicates the total number of champions associated with or involved in a given context or entity.
-
B.
worldConstructorsChampionThatSeason
Indicates that the subject was the Constructors' Champion in the specified racing season.
-
C.
leagueChampionFranchisePennantCount
Indicates the number of league championship pennants won by a given franchise.
-
D.
championRegularSeasonWins
Indicates that an entity is the champion based on having the highest number of regular season wins.
-
E.
numberOfWinnersPerSeason
chosen
Indicates the relationship that specifies how many winners are associated with each individual season.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: April 27, 2026, 8:12 p.m.