Triple

T6405870
Position Surface form Disambiguated ID Type / Status
Subject Ben Stokes E144175 entity
Predicate notableInnings P28663 FINISHED
Object 135* vs Australia at Headingley in 2019 Ashes 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: 135* vs Australia at Headingley in 2019 Ashes | Statement: [Ben Stokes, notableInnings, 135* vs Australia at Headingley in 2019 Ashes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableInnings
Context triple: [Ben Stokes, notableInnings, 135* vs Australia at Headingley in 2019 Ashes]
  • A. notableEventInning chosen
    Indicates the specific inning during which a notable or significant event occurred in a game.
  • B. notableBatter
    Indicates that the subject is a batter who is particularly prominent, distinguished, or noteworthy in the context of batting.
  • C. notablePlay
    Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
  • D. notablePitch
    Indicates that an entity is recognized for having a particularly significant or noteworthy pitch, offer, or proposal in a given context.
  • E. notableStatistic
    Indicates that a particular statistic is especially significant or noteworthy in relation to the subject.
  • 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_69c008dc56fc81908d43ffcc11d73bdd completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c068b22c74819092228010708aec6b completed March 22, 2026, 10:09 p.m.
PD Predicate disambiguation batch_69c060f40ecc8190b1df17b96767675c completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:35 p.m.