Triple
T36270978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Over |
E892671
|
entity |
| Predicate | fieldingSideSelection |
P186005
|
FINISHED |
| Object | other team if it loses the toss |
—
|
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: other team if it loses the toss | Statement: [Super Over, fieldingSideSelection, other team if it loses the toss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldingSideSelection Context triple: [Super Over, fieldingSideSelection, other team if it loses the toss]
-
A.
fieldingSidePerspective
Indicates the viewpoint or frame of reference associated with the team or side that is currently fielding or defending in a game or play.
-
B.
fieldingAbility
Indicates the level or quality of an entity’s skill and effectiveness in performing fielding actions in a game or sport.
-
C.
fieldingSpecialty
Indicates a player's particular area of expertise or primary role when performing defensive (fielding) duties in a sport.
-
D.
fieldedIn
Indicates that an entity was deployed, presented, or put into active use within a particular context, event, or domain.
-
E.
battingSideSelection
Indicates the choice of which side or team will bat in a game or innings.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:09 p.m.