Triple
T35863208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1979 European Cup Final |
E1037009
|
entity |
| Predicate | Nottingham Forest European Cup titlesAfterMatch |
P144486
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [1979 European Cup Final, Nottingham Forest European Cup titlesAfterMatch, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Nottingham Forest European Cup titlesAfterMatch Context triple: [1979 European Cup Final, Nottingham Forest European Cup titlesAfterMatch, 1]
-
A.
yearOfEuropeanCupWinnersCupTitle
Indicates the specific year in which an entity won the European Cup Winners' Cup title.
-
B.
wonEuropeanCupWinnersCup
Indicates that the subject has won the European Cup Winners' Cup football competition.
-
C.
UEFAInterCitiesFairsCupTitles
Indicates the number of UEFA Inter-Cities Fairs Cup titles an entity has won.
-
D.
ChelseaFirstEuropeanCupTitle
Indicates that the event marks Chelsea’s first-ever European Cup title victory.
-
E.
winnerFirstEuropeanCupTitle
chosen
Indicates that the subject is the team or individual who won their first European Cup title in the referenced competition or season.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:06 p.m.