Triple
T18250091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelsea 2004–05 Premier League title-winning season |
E437065
|
entity |
| Predicate | LeagueCupOutcome |
P51310
|
FINISHED |
| Object | winners |
—
|
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: winners | Statement: [Chelsea 2004–05 Premier League title-winning season, LeagueCupOutcome, winners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LeagueCupOutcome Context triple: [Chelsea 2004–05 Premier League title-winning season, LeagueCupOutcome, winners]
-
A.
leagueCupResult
chosen
Indicates the outcome or standing a team or participant achieved in a specific league cup competition.
-
B.
leagueCup
Indicates that an entity is a cup-style competition organized within or by a specific league.
-
C.
FA CupFinalScore
Indicates the final match score in an FA Cup competition, specifying how many goals each team scored in the deciding game.
-
D.
FA CupFinalOpponent
Indicates that one entity was the opposing team faced by the other entity in an FA Cup final match.
-
E.
FA CupWinnerWith
Indicates a relationship where a team is identified as having won the FA Cup together with (i.e., in association with) a particular season, year, or related contextual attribute.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd8065b08190ae8d37102141f470 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:33 a.m.