Triple

T13447858
Position Surface form Disambiguated ID Type / Status
Subject Tyrus Cobb E320530 entity
Predicate battingAverageRecord P7538 FINISHED
Object .366 career batting average 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: .366 career batting average | Statement: [Tyrus Cobb, battingAverageRecord, .366 career batting average]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: battingAverageRecord
Context triple: [Tyrus Cobb, battingAverageRecord, .366 career batting average]
  • A. battingAverage
    Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
  • B. odiBattingAverage
    Indicates the batting average a player has achieved in One Day International (ODI) cricket matches.
  • C. careerBattingAverage chosen
    Indicates the long-term batting performance of a player, calculated as their total hits divided by total at-bats over their entire career.
  • D. battingAverageType
    Indicates the type or category of a batting average associated with a player or performance (e.g., season, career, situational).
  • E. testBattingAverage
    Indicates that an entity evaluates or measures the batting average performance of another entity or 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaef758b08190b9aa5ec7082cd417 completed April 12, 2026, 2:40 p.m.
PD Predicate disambiguation batch_69d9a03ce03481908c61094f0cc0c158 completed April 11, 2026, 1:13 a.m.
Created at: April 9, 2026, 9:41 p.m.