Triple
T17960815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ODI |
E449074
|
entity |
| Predicate | usesLimitedOvers |
P57803
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ODI, usesLimitedOvers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLimitedOvers Context triple: [ODI, usesLimitedOvers, yes]
-
A.
usesLimitedOversRules
chosen
Indicates that the action or event is conducted under limited-overs rules, typically involving a fixed maximum number of overs per side.
-
B.
typicalInningsOversLimit
Indicates the standard maximum number of overs allotted to an innings in a given cricket format or competition.
-
C.
usesDuckworthLewisSternMethod
Indicates that an entity determines outcomes or targets in a limited-overs cricket match using the Duckworth–Lewis–Stern (DLS) rain-affected scoring method.
-
D.
steppedDownAsLimitedOversCaptain
Indicates that an entity resigned from the role of captain specifically for limited-overs formats of the sport.
-
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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b131fa8481908cd756f350eb6359 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.