Triple
T6198116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottingham Forest F.C. |
E138559
|
entity |
| Predicate | leagueCupWinningSeason |
P41878
|
FINISHED |
| Object | 1977–78 |
—
|
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: 1977–78 | Statement: [Nottingham Forest F.C., leagueCupWinningSeason, 1977–78]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueCupWinningSeason Context triple: [Nottingham Forest F.C., leagueCupWinningSeason, 1977–78]
-
A.
wonLeagueCup
Indicates that a team or competitor achieved victory in a specific league cup competition or tournament.
-
B.
seasonOfCompetitionWon
chosen
Indicates the specific season of a competition in which an entity achieved a victory or championship.
-
C.
lastSeasonChampion
Indicates that the subject is the champion or winner of the immediately preceding season of the relevant competition or event.
-
D.
wonLeagueInTrebleSeason
Indicates that a team won its domestic league title as part of a season in which it achieved a treble (three major trophies).
-
E.
firstSeasonChampions
Indicates that the subject entity won the championship in the first season of the relevant competition or series.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06251b47881909bd8d2ea37541959 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.