Triple

T17960814
Position Surface form Disambiguated ID Type / Status
Subject ODI E449074 entity
Predicate cricketFormatFamily P57803 FINISHED
Object one-day cricket 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: one-day cricket | Statement: [ODI, cricketFormatFamily, one-day cricket]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cricketFormatFamily
Context triple: [ODI, cricketFormatFamily, one-day cricket]
  • A. playedFormat
    Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
  • B. worldCupFormat
    Indicates the specific structure, rules, and progression system used to organize and play a given World Cup competition.
  • C. usesLimitedOversRules chosen
    Indicates that the action or event is conducted under limited-overs rules, typically involving a fixed maximum number of overs per side.
  • D. competitionFormat
    Indicates the specific structure or ruleset under which a competition is organized and conducted.
  • E. traditionalCricketTeam
    Indicates that an entity is a cricket team organized and composed according to customary or historically established rules and structures of the sport.
  • 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.