Triple

T2790923
Position Surface form Disambiguated ID Type / Status
Subject Madison Bumgarner E61925 entity
Predicate brokeIntoRotation P43616 FINISHED
Object 2010 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: 2010 | Statement: [Madison Bumgarner, brokeIntoRotation, 2010]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: brokeIntoRotation
Context triple: [Madison Bumgarner, brokeIntoRotation, 2010]
  • A. spontaneouslyBrokenBy
    Indicates that a symmetry or property is not explicitly violated by the underlying laws but is instead broken by the system’s ground state or configuration due to spontaneous symmetry breaking caused by the specified entity or mechanism.
  • B. broken
    Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
  • C. rotatedMoreFrequentlyThan
    Indicates that one entity undergoes rotation or is turned around its axis more often within a given time period than another entity.
  • D. hasChaoticRotation
    Indicates that an object rotates in a highly irregular, unpredictable manner rather than following a stable, consistent spin.
  • E. rotationType
    Indicates the specific kind or mode of rotational movement or orientation applied in a given context.
  • 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_69ab4b7f51d881908768300ebd2fbdae completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdeea881481908d759c72798a50fb completed March 7, 2026, 8:16 a.m.
PD Predicate disambiguation batch_69abdd025c948190a97dd961a9592bac completed March 7, 2026, 8:08 a.m.
PDg Predicate description generation batch_69abdee94c2081908e5075e87e70780a completed March 7, 2026, 8:16 a.m.
Created at: March 6, 2026, 9:58 p.m.