Triple
T1332179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga MX |
E28666
|
entity |
| Predicate | matchPointsForDraw |
P8178
|
FINISHED |
| Object | 1 |
—
|
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 | Statement: [Liga MX, matchPointsForDraw, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchPointsForDraw Context triple: [Liga MX, matchPointsForDraw, 1]
-
A.
matchPointsDraw
chosen
Indicates that the entities receive or share an equal number of points as a result of a drawn or tied match.
-
B.
openingMatchScore
Indicates the degree of similarity or compatibility between an opening (e.g., a position, role, or opportunity) and a given candidate or item, typically expressed as a numeric score.
-
C.
matchupFrequency
Indicates how often a particular pair or set of entities are matched or paired against each other within a given context or timeframe.
-
D.
pointsForWin
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
E.
odiMatchesPlayed
Indicates the number of One Day International (ODI) cricket matches that have been played by or between the referenced entities.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1e7f1388190a6e4eb65a7997380 |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.