Triple

T4741408
Position Surface form Disambiguated ID Type / Status
Subject Ted Williams E105250 entity
Predicate lastPlayerToHit400Plus P51313 FINISHED
Object last MLB player to hit over .400 in a season (.406 in 1941) 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: last MLB player to hit over .400 in a season (.406 in 1941) | Statement: [Ted Williams, lastPlayerToHit400Plus, last MLB player to hit over .400 in a season (.406 in 1941)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lastPlayerToHit400Plus
Context triple: [Ted Williams, lastPlayerToHit400Plus, last MLB player to hit over .400 in a season (.406 in 1941)]
  • A. lastPlayerToHit406InSeason chosen
    Indicates the player who was the most recent one to achieve a .406 batting average over the course of a single season.
  • B. battedOver300Seasons
    Indicates that a player achieved a batting average over .300 in one or more seasons.
  • C. dateOf100PointGame
    Indicates the date on which a specific 100-point game occurred.
  • D. reached600HomeRuns
    Indicates that an entity has achieved a career total of at least 600 home runs.
  • E. scored100PointsInAGame
    Indicates that an entity achieved a total of 100 points in a single game or match.
  • 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_69bd43ef87a48190a5bc3600711aa032 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64a5f3548190a6acf1dcfd64d11d completed March 20, 2026, 3:15 p.m.
PD Predicate disambiguation batch_69bd6221c3b881908604f35f8de6f16b completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:19 p.m.