Triple
T20715344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roses Match |
E509155
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cricket 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: cricket rivalry Context triple: [Roses Match, instanceOf, cricket rivalry]
-
A.
rugby union rivalry
A rugby union rivalry is a recurring, often historically rooted competitive relationship between two rugby union teams or nations, characterized by intense matches, strong fan engagement, and cultural or regional significance beyond ordinary fixtures.
-
B.
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.
-
C.
domestic cricket competition
A domestic cricket competition is an organized series of cricket matches played within a single country between regional, state, or club teams to determine national champions and develop local talent.
-
D.
rugby league rivalry
A rugby league rivalry is a recurring, often intense competitive relationship between two rugby league teams, fueled by historical, geographic, cultural, or competitive factors that heighten the significance of their matches.
-
E.
cricket match
A cricket match is a competitive game between two teams where players alternately bat and bowl/field according to the rules of cricket to score more runs than the opposition within a specified format and duration.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:15 p.m.