Triple
T22665463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 2010–11 |
E559770
|
entity |
| Predicate | titleNumberForChampions |
P114843
|
FINISHED |
| Object | 19 |
—
|
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: 19 | Statement: [Premier League 2010–11, titleNumberForChampions, 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleNumberForChampions Context triple: [Premier League 2010–11, titleNumberForChampions, 19]
-
A.
championCityTitleNumber
Indicates the ordinal number of championship titles that a particular city has won or holds in a given competition or league.
-
B.
consecutiveTitleNumberForChampion
Indicates that the associated number represents how many titles a champion has won consecutively up to that point.
-
C.
championshipNumberForTeam
chosen
Indicates the total number of championships that a given team has won.
-
D.
titleNumber
Indicates the numerical designation or sequence number assigned to a title within an ordered set of titles.
-
E.
totalChampionsCount
Indicates the total number of champions associated with or involved in a given context or entity.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781b3dbc8190a312843cf8c1bfc6 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:08 p.m.