Triple
T14319771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hundred |
E355051
|
entity |
| Predicate | numberOfBallsPerInnings |
P113969
|
FINISHED |
| Object | 100 |
—
|
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: 100 | Statement: [The Hundred, numberOfBallsPerInnings, 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfBallsPerInnings Context triple: [The Hundred, numberOfBallsPerInnings, 100]
-
A.
typicalInningsOversLimit
Indicates the standard maximum number of overs allotted to an innings in a given cricket format or competition.
-
B.
ballsAndStrikes
Indicates the relationship between a pitch and how it is judged in baseball as either a ball or a strike.
-
C.
tieInnings
Indicates that two or more teams or players have finished an innings with the same score, resulting in no winner for that innings.
-
D.
usesInnings
Indicates that one entity employs or incorporates another entity within the context or structure of innings (e.g., in a game, match, or statistical framework).
-
E.
minimumInningsRequirement
Indicates that a player must have pitched or played at least a specified minimum number of innings to qualify for a particular status, record, or statistical consideration.
- 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.