Triple
T20294285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019–20 Premier League season |
E510105
|
entity |
| Predicate | titleClinchedRoundsRemaining |
P139569
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [2019–20 Premier League season, titleClinchedRoundsRemaining, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleClinchedRoundsRemaining Context triple: [2019–20 Premier League season, titleClinchedRoundsRemaining, 7]
-
A.
numberOfRoundsToWin
Indicates the number of rounds an entity must win in a competition or game to be declared the overall winner.
-
B.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
C.
roundOfChampionship
Indicates the specific stage or round within a championship competition in which an event, match, or result takes place.
-
D.
clinchingGameState
Indicates a game state in which one side can secure a series, title, or advancement with a win (or, less commonly, face elimination with a loss).
-
E.
numberOfKnockouts
Indicates the total count of times an entity has defeated opponents by knockout.
- 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67704262c8190bc903b733d849881 |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:13 a.m.