Triple
T21486424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limited overs cricket |
E530127
|
entity |
| Predicate | typicalInningsPerTeam |
P123915
|
FINISHED |
| Object | one innings |
—
|
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: one innings | Statement: [Limited overs cricket, typicalInningsPerTeam, one innings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInningsPerTeam Context triple: [Limited overs cricket, typicalInningsPerTeam, one innings]
-
A.
numberOfInningsPerSide
chosen
Indicates the number of innings that each side or team is allotted to play in a game or match.
-
B.
typicalInningsOversLimit
Indicates the standard maximum number of overs allotted to an innings in a given cricket format or competition.
-
C.
numberOfBallsPerInnings
Indicates the quantity of balls delivered or played during a single innings.
-
D.
typicalNumberOfMatchesPerSeries
Indicates the usual or standard count of matches that are played within a single series.
-
E.
tieInnings
Indicates that two or more teams or players have finished an innings with the same score, resulting in no winner for that innings.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea370adc8190b79fe26e2eba1dca |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.