Triple
T26804609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SK Rapid Wien |
E671193
|
entity |
| Predicate | reachedFinalSeason |
P161493
|
FINISHED |
| Object | 1984–85 European Cup Winners' Cup |
—
|
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: 1984–85 European Cup Winners' Cup | Statement: [SK Rapid Wien, reachedFinalSeason, 1984–85 European Cup Winners' Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedFinalSeason Context triple: [SK Rapid Wien, reachedFinalSeason, 1984–85 European Cup Winners' Cup]
-
A.
lastCompletedSeason
Indicates the most recent season of an ongoing or episodic series that has been fully finished or concluded.
-
B.
seasonFinaleOf
Indicates that one event, episode, or installment serves as the concluding or final part of a particular season of a series or competition.
-
C.
endSeason
Indicates the action or event of bringing a particular season, series, or period to a close.
-
D.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
-
E.
finalSeasonPremiereYear
Indicates the calendar year in which the first episode of an entity’s final season was originally released or broadcast.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a1b6c348190a54a0ac2a0b463b5 |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6142a0b988190b404d078f73c3cb9 |
completed | May 2, 2026, 3:11 p.m. |
Created at: April 27, 2026, 4:25 a.m.