Triple
T37923211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitropa Cup |
E946019
|
entity |
| Predicate | notableClubParticipant |
—
|
GENERATED |
| Object | Rapid Wien |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableClubParticipant Context triple: [Mitropa Cup, notableClubParticipant, Rapid Wien]
-
A.
hasNotableClubParticipant
chosen
Indicates that an entity has a club in which another entity participates in a way considered notable or significant.
-
B.
notableClub
Indicates that an entity is prominently associated with or recognized for membership in a particular club or organization.
-
C.
notableParticipant
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
-
D.
notableOpponentTeamMember
Indicates that a specific team member is recognized as a particularly significant or noteworthy opponent in relation to another entity or context.
-
E.
notableBowlParticipant
Indicates that an entity has participated in a bowl game in a way considered notable or significant.
- F. None of above.
Provenance (1 batch)
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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.