Triple
T26099812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England vs Australia |
E658365
|
entity |
| Predicate | AshesSeriesFrequency |
P30335
|
FINISHED |
| Object | biennial or quadrennial |
—
|
LITERAL 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: biennial or quadrennial | Statement: [England vs Australia, AshesSeriesFrequency, biennial or quadrennial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AshesSeriesFrequency Context triple: [England vs Australia, AshesSeriesFrequency, biennial or quadrennial]
-
A.
typicalNumberOfMatchesPerSeries
Indicates the usual or standard count of matches that are played within a single series.
-
B.
numberOfInningsPerSide
Indicates the number of innings that each side or team is allotted to play in a game or match.
-
C.
gamesFrequency
chosen
Indicates how often the related entities engage in playing games together or participate in game-related activities.
-
D.
cricketWorldCupAppearances
Indicates the number of times an entity has participated in the Cricket World Cup tournament.
-
E.
teamsPerSeries
Indicates the number of teams that participate in each series within a competition or event.
- F. None of above.
Provenance (3 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6073a39408190994ac1c8983a7c0b |
completed | May 2, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:54 p.m.