Triple
T5494479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC Cricket World Cup |
E144177
|
entity |
| Predicate | oversPerInnings |
P57804
|
FINISHED |
| Object | 50 |
—
|
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: 50 | Statement: [ICC Cricket World Cup, oversPerInnings, 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oversPerInnings Context triple: [ICC Cricket World Cup, oversPerInnings, 50]
-
A.
oversPerSide
Indicates the number of overs allocated to each side (team or player) in a match or contest.
-
B.
typicalInningsOversLimit
chosen
Indicates the standard maximum number of overs allotted to an innings in a given cricket format or competition.
-
C.
setsPerMatch
Indicates the number of sets that are played or scheduled to be played in a single match.
-
D.
halfInning
Indicates the specific offensive or defensive segment of an inning in a game, typically distinguishing the top (visiting team at bat) from the bottom (home team at bat).
-
E.
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).
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f08c2a4819093e772a1497c7ecc |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:31 p.m.