Triple

T31572301
Position Surface form Disambiguated ID Type / Status
Subject 1930 Major League Baseball season E805597 entity
Predicate leagueBattingAverage P14861 FINISHED
Object .296 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: .296 | Statement: [1930 Major League Baseball season, leagueBattingAverage, .296]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: leagueBattingAverage
Context triple: [1930 Major League Baseball season, leagueBattingAverage, .296]
  • A. odiBattingAverage
    Indicates the batting average a player has achieved in One Day International (ODI) cricket matches.
  • B. careerBattingAverage
    Indicates the long-term batting performance of a player, calculated as their total hits divided by total at-bats over their entire career.
  • C. battingAverage chosen
    Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
  • D. ledLeagueInBattingAverage
    Indicates that an entity achieved the highest batting average in a particular league over a specified season or time period.
  • E. battingAverageCategory
    Indicates the classification of an entity’s batting average into a defined performance category (e.g., low, medium, high).
  • 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_69f348d2ee94819091918d1789398c29 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6db6af1d88190989810182354d60f completed May 3, 2026, 5:21 a.m.
PD Predicate disambiguation batch_69f6d82d068c8190940a3200ed760e38 completed May 3, 2026, 5:07 a.m.
Created at: April 30, 2026, 10:20 p.m.