Triple
T9481843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Necaxa |
E228659
|
entity |
| Predicate | league |
P888
|
FINISHED |
| Object | Liga MX |
E28666
|
NE 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: Liga MX | Statement: [Necaxa, league, Liga MX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Liga MX Context triple: [Necaxa, league, Liga MX]
-
A.
Liga MX
chosen
Liga MX is the top professional football (soccer) division in Mexico, featuring the country’s most prominent clubs.
-
B.
Liga de Balompié Mexicano
Liga de Balompié Mexicano is an independent professional football league in Mexico that operates outside the traditional federation-sanctioned league structure.
-
C.
Liga Premier de México
Liga Premier de México is a lower-division professional football league in Mexico that serves as part of the country's promotion and development structure beneath the top tiers.
-
D.
Liga de Expansión MX
Liga de Expansión MX is Mexico’s second-tier professional football league, created as a developmental and transitional competition beneath Liga MX.
-
E.
Copa MX
Copa MX was a Mexican domestic cup competition in which professional football clubs from various divisions competed in a knockout-style tournament.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd804af6d08190a281cb27407c791c |
completed | April 1, 2026, 8:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d12cfebb6c8190af3296c7bfd8b3e4 |
completed | April 4, 2026, 3:23 p.m. |
Created at: March 30, 2026, 7:55 p.m.