Triple
T16531472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One-Day Cup |
E401575
|
entity |
| Predicate | numberOfInningsPerSide |
P123915
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [One-Day Cup, numberOfInningsPerSide, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfInningsPerSide Context triple: [One-Day Cup, numberOfInningsPerSide, 1]
-
A.
numberOfBallsPerInnings
Indicates the quantity of balls delivered or played during a single innings.
-
B.
typicalInningsOversLimit
Indicates the standard maximum number of overs allotted to an innings in a given cricket format or competition.
-
C.
numberOfGamesInMatch
Indicates the total count of individual games that make up a single match.
-
D.
tieInnings
Indicates that two or more teams or players have finished an innings with the same score, resulting in no winner for that innings.
-
E.
setsPerMatch
Indicates the number of sets that are played or scheduled to be played in a single match.
- F. None of above. chosen
Provenance (4 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed8075c81908ff47396879abd0c |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.