Triple
T18022894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Splash (aquatics rivalry with Stanford) |
E431169
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aquatics 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: aquatics rivalry Context triple: [Big Splash (aquatics rivalry with Stanford), instanceOf, aquatics rivalry]
-
A.
swimming competition
A swimming competition is an organized event where swimmers race against each other in designated strokes and distances to achieve the fastest time and win rankings or medals.
-
B.
aquatic sport
An aquatic sport is a competitive or recreational physical activity performed in, on, or under water, often requiring specialized skills, equipment, and adherence to specific rules.
-
C.
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.
-
D.
para swimming competition
A para swimming competition is an organized sporting event where swimmers with physical, visual, or intellectual impairments race in classified categories under standardized rules to ensure fair and inclusive competition.
-
E.
ice hockey rivalry
An ice hockey rivalry is a competitive and often intense ongoing relationship between two ice hockey teams, fueled by repeated matchups, historical context, geographic proximity, or cultural factors that heighten fan and player emotions.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:24 a.m.