Triple
T23688841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football League Cup 2000–01 |
E585242
|
entity |
| Predicate | winnerSeasonAchievement |
P97701
|
FINISHED |
| Object | treble |
—
|
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: treble | Statement: [Football League Cup 2000–01, winnerSeasonAchievement, treble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerSeasonAchievement Context triple: [Football League Cup 2000–01, winnerSeasonAchievement, treble]
-
A.
winnerEventualAchievement
Indicates that an entity ultimately attains victory or success as the final outcome of a process, competition, or sequence of events.
-
B.
achievementInSeason
chosen
Indicates a relationship where a specific achievement occurs within or is associated with a particular season or seasonal period.
-
C.
trophyWonWith
Indicates that a particular trophy or award was achieved using, through, or in association with a specified means, tool, team, or context.
-
D.
wonSeasonOf
Indicates that one entity emerged as the overall winner of a particular season of a competition, show, or series involving the other entity.
-
E.
awardInSeason
Indicates that an award was given during a specific season or seasonal period.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c0a218819096c2d174b004c47d |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.