Triple
T27096772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga MX Apertura 2021 |
E686324
|
entity |
| Predicate | hasPlayoffsStage |
P18796
|
FINISHED |
| Object | Liguilla |
—
|
NE NERFINISHED |
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: Liguilla | Statement: [Liga MX Apertura 2021, hasPlayoffsStage, Liguilla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayoffsStage Context triple: [Liga MX Apertura 2021, hasPlayoffsStage, Liguilla]
-
A.
hasPlayoffsWith
Indicates that two entities participate together in the same playoff series, bracket, or postseason competition.
-
B.
hasPlayoffRoundBefore
Indicates that one playoff round occurs earlier in the sequence than another playoff round within the same competition or season.
-
C.
hasPlayOffsFor
Indicates that an entity organizes or includes playoff competitions specifically for another entity (such as a league, season, or division).
-
D.
hasPositionInPlayoffs
Indicates that an entity holds a specific rank or standing within a playoff competition or bracket.
-
E.
hasPlayOffs
chosen
Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 8:44 a.m.