Triple
T27096778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga MX Apertura 2021 |
E686324
|
entity |
| Predicate | hasFinalAggregateScore |
P2625
|
FINISHED |
| Object | 3–3 |
—
|
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: 3–3 | Statement: [Liga MX Apertura 2021, hasFinalAggregateScore, 3–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalAggregateScore Context triple: [Liga MX Apertura 2021, hasFinalAggregateScore, 3–3]
-
A.
hasScoreAvailable
Indicates that a score or rating for the relevant entity is present and can be accessed.
-
B.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
C.
hasScoreRecord
Indicates that an entity is associated with a specific score entry or scoring record.
-
D.
recordAggregateScore
Indicates recording a combined or total score derived from multiple individual scores or components.
-
E.
hasWinningScore
Indicates that one entity possesses a score that is sufficient to win in a given competition, game, or scoring context.
- 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_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 27, 2026, 8:44 a.m.