Triple

T24734629
Position Surface form Disambiguated ID Type / Status
Subject 1994 Major League Baseball season E618376 entity
Predicate tonyGwynnBattingAverage P14861 FINISHED
Object .394 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: .394 | Statement: [1994 Major League Baseball season, tonyGwynnBattingAverage, .394]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tonyGwynnBattingAverage
Context triple: [1994 Major League Baseball season, tonyGwynnBattingAverage, .394]
  • A. odiBattingAverage
    Indicates the batting average a player has achieved in One Day International (ODI) cricket matches.
  • B. 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.
  • C. careerBattingAverage
    Indicates the long-term batting performance of a player, calculated as their total hits divided by total at-bats over their entire career.
  • D. testBattingAverage
    Indicates that an entity evaluates or measures the batting average performance of another entity or subject.
  • 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_69e2fab772608190b74163751047ff50 completed April 18, 2026, 3:29 a.m.
NER Named-entity recognition batch_69f410a25ab88190a72db43043c1f6ff completed May 1, 2026, 2:32 a.m.
PD Predicate disambiguation batch_69f40ef612c88190ab2f3f08d4a92018 completed May 1, 2026, 2:24 a.m.
Created at: April 18, 2026, 4:03 a.m.