Triple
T1415381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle Sounders FC and Vancouver Whitecaps FC |
E31902
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | association football rivalry |
C778
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: association football rivalry Context triple: [Seattle Sounders FC and Vancouver Whitecaps FC, instanceOf, association football rivalry]
-
A.
sports rivalry
chosen
A sports rivalry is a competitive relationship between teams, athletes, or fan bases characterized by repeated contests, heightened emotions, and historical or cultural significance that intensifies their matchups.
-
B.
soccer rivalry trophy
A soccer rivalry trophy is a symbolic award contested between two or more soccer teams, typically given to the winner of their recurring matches to commemorate and intensify their competitive rivalry.
-
C.
club football competition
A club football competition is an organized tournament or league in which football clubs compete against each other under a defined set of rules and structure to determine rankings, titles, or championships.
-
D.
association football club
An association football club is an organized team entity that competes in the sport of soccer under a common name, management, and identity, typically participating in official leagues and tournaments.
-
E.
association football trophy
An association football trophy is a physical award, often a cup or shield, presented to a team or individual to symbolize victory or achievement in a football competition or tournament.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:59 p.m.