Triple
T27267393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga MX Clausura 2022 |
E687942
|
entity |
| Predicate | topScorerCompetition |
P162293
|
FINISHED |
| Object | Liga MX top scorers 2022 Clausura |
—
|
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: Liga MX top scorers 2022 Clausura | Statement: [Liga MX Clausura 2022, topScorerCompetition, Liga MX top scorers 2022 Clausura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topScorerCompetition Context triple: [Liga MX Clausura 2022, topScorerCompetition, Liga MX top scorers 2022 Clausura]
-
A.
topScorer
Indicates that the subject is the individual with the highest score among a specified group or in a particular context.
-
B.
topScorerPoints
Indicates the number of points scored by the top-scoring entity in a given context or event.
-
C.
topGoalScorerGoals
Indicates the number of goals scored by the top goal scorer in a given context or competition.
-
D.
isAmongTopScorers
Indicates that an entity ranks within the highest-performing group based on a scoring or evaluation metric.
-
E.
goalScorer
Indicates that the subject is the player who scored a particular goal in a game or match.
- F. None of above. chosen
Provenance (4 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f626f45a1481909200fc3f7fda8a61 |
completed | May 2, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 10:56 a.m.