Triple
T26301224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omnilife-Chivas Group |
E661562
|
entity |
| Predicate | sportDisciplineManaged |
P78541
|
FINISHED |
| Object | association football |
—
|
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: association football | Statement: [Omnilife-Chivas Group, sportDisciplineManaged, association football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportDisciplineManaged Context triple: [Omnilife-Chivas Group, sportDisciplineManaged, association football]
-
A.
sportDisciplineScope
Indicates the specific sport discipline or category within which a given relationship, rule, or activity is defined or applies.
-
B.
sportsDisciplineCoachedOrManaged
Indicates that a person has coached or managed a particular sports discipline or type of sport.
-
C.
sportTypeGoverned
chosen
Indicates that a governing body or organization has regulatory authority over a particular type of sport.
-
D.
sportOrganizationManaged
Indicates that one entity is responsible for directing, operating, or overseeing the activities and affairs of a sports-related organization.
-
E.
esportDiscipline
Indicates that one entity is a specific esports game or discipline in which the other entity participates or is involved.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60eb2b658819086b8ad443c0a9275 |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 10:15 p.m.