Triple
T27096781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga MX Apertura 2021 |
E686324
|
entity |
| Predicate | usesAwayGoalsRuleInFinal |
P52769
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Liga MX Apertura 2021, usesAwayGoalsRuleInFinal, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAwayGoalsRuleInFinal Context triple: [Liga MX Apertura 2021, usesAwayGoalsRuleInFinal, false]
-
A.
usesAwayGoalsRule
chosen
Indicates that a competition or match outcome is decided using the away goals rule, where goals scored by a team in away games serve as a tiebreaker.
-
B.
goldenGoalRuleUsed
Indicates that the outcome of a match or competition was determined using the golden goal rule, where the first score in extra time immediately ends the game.
-
C.
penaltyGoalPoints
Indicates that points are awarded for a goal scored from a penalty situation.
-
D.
usesGoalDifferenceTiebreaker
Indicates that when entities are tied, their ranking or outcome is decided based on the difference between goals scored and goals conceded.
-
E.
finalScoreAway
Indicates the final score achieved by the away entity (e.g., team or participant) in a contest or event.
- 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_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 8:44 a.m.