Triple
T23843487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football League Cup 1983–84 |
E591052
|
entity |
| Predicate | finalManagerOfChampion |
P154156
|
FINISHED |
| Object | Joe Fagan |
—
|
NE NERFINISHED |
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: Joe Fagan | Statement: [Football League Cup 1983–84, finalManagerOfChampion, Joe Fagan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalManagerOfChampion Context triple: [Football League Cup 1983–84, finalManagerOfChampion, Joe Fagan]
-
A.
finalChampion
Indicates that an entity is the ultimate winner or last remaining champion in a competition or series of contests.
-
B.
finalsChampion
Indicates that an entity is the winner or champion of a particular final match, series, or tournament.
-
C.
generalManagerOfChampion
Indicates that one entity serves as the general manager responsible for overseeing and managing the champion entity.
-
D.
finalManOfTheMatch
Indicates that the referenced person was chosen as the ultimate or concluding Man of the Match for a particular game or series.
-
E.
defendingChampion
Indicates that an entity currently holds a title or championship and is defending it against challengers.
- F. None of above. chosen
Provenance (4 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c8898a0c8190b4d55852fc30260f |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:09 p.m.