Triple

T2740853
Position Surface form Disambiguated ID Type / Status
Subject Bobby Doerr E60744 entity
Predicate missedSeasonsDueToMilitaryService P41296 FINISHED
Object 1945 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: 1945 | Statement: [Bobby Doerr, missedSeasonsDueToMilitaryService, 1945]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: missedSeasonsDueToMilitaryService
Context triple: [Bobby Doerr, missedSeasonsDueToMilitaryService, 1945]
  • A. suspendedForSeason
    Indicates that an entity (typically a player or participant) is prohibited from taking part in all activities or competitions for the duration of an entire season.
  • B. hasMilitaryServiceEnd
    Indicates the date or point in time at which an entity’s period of military service concludes.
  • C. hasMilitaryServiceStart
    Indicates the date or point in time when an entity’s period of military service began.
  • D. militaryStatus
    Indicates the relationship between an entity and a military organization in terms of service condition, such as active duty, reserve, veteran, or non-military status.
  • E. militaryBranchEligibility
    Indicates that an entity meets the required conditions to serve in a specified branch of the military.
  • F. None of above. chosen

Provenance (4 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_69ab4b77febc819095603eb012cd141b completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdb2f210881909126307cc92ebfef completed March 7, 2026, 8 a.m.
PD Predicate disambiguation batch_69abd829f1e88190aab1d54f87c69714 completed March 7, 2026, 7:47 a.m.
PDg Predicate description generation batch_69abd8dd05c48190b4f90031642c4091 completed March 7, 2026, 7:50 a.m.
Created at: March 6, 2026, 9:56 p.m.