Triple
T7349043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Oval |
E169447
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international cricket venue |
C22052
|
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: international cricket venue Context triple: [The Oval, instanceOf, international cricket venue]
-
A.
international cricket competition
An international cricket competition is a formally organized series of cricket matches between national or representative teams from different countries, played under agreed rules and schedules to determine rankings, titles, or championships.
-
B.
One Day International cricket tournament
A One Day International cricket tournament is a limited-overs competition between national teams, where each side typically plays 50 overs per match in a structured series of games culminating in a champion.
-
C.
Twenty20 International cricket team
A Twenty20 International cricket team is a national side officially recognized by the sport’s governing body to compete in the Twenty20 format of international cricket, playing matches of up to 20 overs per innings under standardized T20I rules.
-
D.
One Day International cricket team
A One Day International cricket team is a national side officially recognized by the ICC to compete in limited-overs matches of up to 50 overs per innings under ODI rules.
-
E.
international rugby league match
An international rugby league match is a competitive game of rugby league played between representative teams from different countries under the governance and rules of the sport’s international bodies.
- F. None of above. chosen
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_69c68a5878888190968ce4d04db8d69f |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:05 p.m.