Triple

T32884031
Position Surface form Disambiguated ID Type / Status
Subject Stan Coveleski E841145 entity
Predicate allowedToUseSpitballAfterBan P79190 FINISHED
Object true 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: true | Statement: [Stan Coveleski, allowedToUseSpitballAfterBan, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allowedToUseSpitballAfterBan
Context triple: [Stan Coveleski, allowedToUseSpitballAfterBan, true]
  • A. allowedToContinueSpitballAfterBan chosen
    Indicates that an entity is permitted to continue informal or speculative discussion (spitballing) even after a ban or prohibition has been imposed.
  • B. useAfterMLB
    Indicates that one entity is used or occurs after a Major League Baseball–related event, period, or context associated with another entity.
  • C. battingRestrictions
    Indicates limitations or special conditions imposed on how an entity is allowed to bat or participate in batting.
  • D. usesKayfabe
    Indicates that one entity presents events, actions, or relationships as part of a staged or scripted narrative, treating them as real for dramatic effect rather than acknowledging them as fictional or prearranged.
  • E. canBypassTaunt
    Indicates that an entity is able to ignore or circumvent a taunt effect that would normally force it to target the taunting source.
  • 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_69f349446e288190a70c05bcc4d81172 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fbbc49da8c8190902bbb05d2477cab completed May 6, 2026, 10:10 p.m.
PD Predicate disambiguation batch_69fbb13f34b08190bbbb220ac1e6e666 completed May 6, 2026, 9:23 p.m.
Created at: May 1, 2026, 1:18 a.m.