Triple
T36270987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Over |
E892671
|
entity |
| Predicate | tieAfterSuperOver |
P108293
|
FINISHED |
| Object | may lead to another Super Over |
—
|
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: may lead to another Super Over | Statement: [Super Over, tieAfterSuperOver, may lead to another Super Over]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieAfterSuperOver Context triple: [Super Over, tieAfterSuperOver, may lead to another Super Over]
-
A.
oversBowled
Indicates that a bowler has delivered a specified number of legal overs in a cricket match.
-
B.
tieInnings
Indicates that two or more teams or players have finished an innings with the same score, resulting in no winner for that innings.
-
C.
battingConditions
Indicates the environmental or situational factors that affect how batting is performed or how effective it is.
-
D.
subsequentInningOutcome
chosen
Indicates the result or event that occurs in the inning immediately following a given reference inning.
-
E.
team1OversFaced
Indicates the total number of overs that the first team has faced while batting in a cricket match.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.