Triple

T16909182
Position Surface form Disambiguated ID Type / Status
Subject Tinker–Evers–Chance double-play combination E410148 entity
Predicate instanceOf P0 FINISHED
Object baseball infield combination C3919 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: baseball infield combination
Context triple: [Tinker–Evers–Chance double-play combination, instanceOf, baseball infield combination]
  • A. baseball infield unit chosen
    A baseball infield unit is the coordinated group of infield players—typically first baseman, second baseman, shortstop, and third baseman—who work together to field ground balls, execute force and tag plays, and defend against bunts and base-stealing within the infield area.
  • B. baseball position
    A baseball position is a specific defensive role assigned to a player on the field, defining their location, responsibilities, and typical actions during play.
  • C. infielder
    An infielder is a baseball or softball player who fields defensive positions on the inner portion of the field, typically including first base, second base, shortstop, and third base.
  • D. baseball play
    A baseball play is a discrete in-game event or sequence of actions involving one or more players that begins with a pitch and results in a change or potential change to the game state, such as outs, advances, or scoring.
  • E. baseball outfield trio
    A baseball outfield trio is the coordinated group of three defensive players—left fielder, center fielder, and right fielder—responsible for covering the outfield, catching fly balls, cutting off hits, and preventing extra-base advances.
  • F. None of above.

Provenance (1 batch)

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_69d886c7b1e481908c3766dfa8c13458 completed April 10, 2026, 5:12 a.m.
Created at: April 10, 2026, 5:30 a.m.