Triple

T4948652
Position Surface form Disambiguated ID Type / Status
Subject Christy Mathewson E111111 entity
Predicate battingAverageAsHitter P14861 FINISHED
Object .215 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: .215 | Statement: [Christy Mathewson, battingAverageAsHitter, .215]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: battingAverageAsHitter
Context triple: [Christy Mathewson, battingAverageAsHitter, .215]
  • A. 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.
  • 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. battingAverageAgainst
    Indicates the average batting performance (e.g., hits per at-bat) that a batter achieves specifically against a particular pitcher, team, or category of opponents.
  • D. SluggingPercentage
    Indicates the rate at which a batter accumulates total bases per at-bat, reflecting their overall power-hitting effectiveness.
  • E. battingStrength
    Indicates the relative power or effectiveness of an entity’s batting performance in a given context.
  • 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_69bd441721cc819085c7e33fe0876818 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd7166bb6c8190a40775ac8bb723a8 completed March 20, 2026, 4:10 p.m.
PD Predicate disambiguation batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa completed March 20, 2026, 3:48 p.m.
Created at: March 20, 2026, 1:31 p.m.