Triple
T37923211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitropa Cup |
E946019
|
entity |
| Predicate | notableClubParticipant |
P198752
|
FINISHED |
| Object | Rapid Wien |
E615608
|
NE 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: Rapid Wien | Statement: [Mitropa Cup, notableClubParticipant, Rapid Wien]
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 (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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410cd4bf748190be299c50e2a80c75 |
completed | June 28, 2026, noon |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.