Triple
T36380166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC Cricket World Cup Qualifier 2023 matches |
E896022
|
entity |
| Predicate | ballCountPerOver |
P113971
|
FINISHED |
| Object | 6 balls |
—
|
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: 6 balls | Statement: [ICC Cricket World Cup Qualifier 2023 matches, ballCountPerOver, 6 balls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballCountPerOver Context triple: [ICC Cricket World Cup Qualifier 2023 matches, ballCountPerOver, 6 balls]
-
A.
ballsPerOverEquivalent
chosen
Indicates the number of balls bowled that is equivalent to one standard over, establishing a conversion between deliveries and overs.
-
B.
numberOfBallsPerInnings
Indicates the quantity of balls delivered or played during a single innings.
-
C.
ballsAndStrikes
Indicates the relationship between a pitch and how it is judged in baseball as either a ball or a strike.
-
D.
typicalInningsOversLimit
Indicates the standard maximum number of overs allotted to an innings in a given cricket format or competition.
-
E.
oversBowled
Indicates that a bowler has delivered a specified number of legal overs in a cricket match.
- 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.