Triple
T16338853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test cricket |
E396743
|
entity |
| Predicate | oversPerInningsLimit |
P57804
|
FINISHED |
| Object | no limit |
—
|
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: no limit | Statement: [Test cricket, oversPerInningsLimit, no limit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oversPerInningsLimit Context triple: [Test cricket, oversPerInningsLimit, no limit]
-
A.
typicalInningsOversLimit
chosen
Indicates the standard maximum number of overs allotted to an innings in a given cricket format or competition.
-
B.
oversPerInningsEquivalent
Indicates the number of overs in cricket that are considered equivalent or comparable across different innings or match contexts.
-
C.
foulLimitPerTeam
Indicates the maximum number of fouls that a single team is allowed to commit within a defined game or competition context.
-
D.
oversPerSide
Indicates the number of overs allocated to each side (team or player) in a match or contest.
-
E.
numberOfBallsPerInnings
Indicates the quantity of balls delivered or played during a single innings.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da08fbc88190a31127d10ca633d6 |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.