Triple
T38429787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football League Cup 1964 |
E903766
|
entity |
| Predicate | goalkeeperOfWinningTeam |
P34552
|
FINISHED |
| Object | Gordon Banks |
—
|
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: Gordon Banks | Statement: [Football League Cup 1964, goalkeeperOfWinningTeam, Gordon Banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalkeeperOfWinningTeam Context triple: [Football League Cup 1964, goalkeeperOfWinningTeam, Gordon Banks]
-
A.
goalkeeperInFinal
Indicates that an entity served as a goalkeeper in the final match of a competition.
-
B.
goaltender
chosen
Indicates a relationship where an entity serves as the goalkeeper or primary defender of the goal for a team in a game or sport.
-
C.
penaltyShootoutWinner
Indicates that one competitor or team is the winner of a match decided by a penalty shootout.
-
D.
goalScorerIn
Indicates that an entity is the player who scored a goal in a particular match or event.
-
E.
titleWinningGoalScorer
Indicates the player who scored the decisive goal that secured a title or championship in a competition.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.