Triple
T14319772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hundred |
E355051
|
entity |
| Predicate | oversPerInningsEquivalent |
P113970
|
FINISHED |
| Object | 16.4 overs |
—
|
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: 16.4 overs | Statement: [The Hundred, oversPerInningsEquivalent, 16.4 overs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oversPerInningsEquivalent Context triple: [The Hundred, oversPerInningsEquivalent, 16.4 overs]
-
A.
strikeoutRate
Indicates the frequency or proportion at which a pitcher (or batter) records strikeouts relative to total opportunities.
-
B.
earnedRunAverage
Indicates the average number of earned runs a pitcher allows per nine innings pitched.
-
C.
battingAverage
Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
-
D.
battedOPS
Indicates the on-base plus slugging (OPS) performance a batter achieved while at the plate, combining how often they reached base with the power of their hits.
-
E.
battingAverageAgainst
Indicates the average batting performance (e.g., hits per at-bat) that a batter achieves specifically against a particular pitcher, team, or category of opponents.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883a93548190ac671b001d15d0bd |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e9ded24819099200349cf80e068 |
completed | April 14, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:13 a.m.