Triple
T13188350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003–04 Premier League |
E313916
|
entity |
| Predicate | championsLosses |
P96140
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [2003–04 Premier League, championsLosses, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championsLosses Context triple: [2003–04 Premier League, championsLosses, 0]
-
A.
championTotalLossesIncludingPostseason
Indicates the total number of games a champion has lost, counting both regular season and postseason losses.
-
B.
mostGamesLostBy
Indicates that one entity holds the record for having lost the greatest number of games to another entity.
-
C.
matchesLostLeague
chosen
Indicates the number of league matches that an entity has lost.
-
D.
careerLosses
Indicates the total number of defeats or losses an entity has accumulated over the course of its entire career.
-
E.
championRegularSeasonWins
Indicates that an entity is the champion based on having the highest number of regular season wins.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:15 p.m.