Triple
T26390038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Cup |
E663384
|
entity |
| Predicate | notableClubWithManyTitles |
P76946
|
FINISHED |
| Object | SK Rapid Wien |
—
|
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: SK Rapid Wien | Statement: [Austrian Cup, notableClubWithManyTitles, SK Rapid Wien]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableClubWithManyTitles Context triple: [Austrian Cup, notableClubWithManyTitles, SK Rapid Wien]
-
A.
notableClubWinner
Indicates that the subject is a club that has achieved a notable or distinguished victory, typically in a significant competition or event.
-
B.
notableAchievementOfClub
Indicates that a particular achievement is recognized as a significant or distinguished accomplishment of a specific club.
-
C.
notableClub
Indicates that an entity is prominently associated with or recognized for membership in a particular club or organization.
-
D.
mostChampionshipTitlesClub
chosen
Indicates that a club holds the highest number of championship titles within a given competition or context.
-
E.
majorTitleWonWithClub
Indicates that a person has won a major title or championship while playing for or being associated with a specific club.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: April 26, 2026, 11:25 p.m.