Triple

T7821756
Position Surface form Disambiguated ID Type / Status
Subject Heinie Zimmerman E181145 entity
Predicate consequenceOfPlay P812 FINISHED
Object Eddie Collins scored on the rundown 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: Eddie Collins scored on the rundown | Statement: [Heinie Zimmerman, consequenceOfPlay, Eddie Collins scored on the rundown]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consequenceOfPlay
Context triple: [Heinie Zimmerman, consequenceOfPlay, Eddie Collins scored on the rundown]
  • A. consequenceForOpponents
    Indicates that one party’s actions or status result in negative outcomes, penalties, or repercussions specifically for their opponents.
  • B. hasConsequence chosen
    Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
  • C. hasConsequenceForPlayer
    Indicates that an event, action, or state produces a specific outcome or effect for the player.
  • D. announcedConsequence
    Indicates that one entity has publicly stated or declared a specific outcome or consequence that will result from an action, event, or condition.
  • E. outcomeOf
    Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
  • 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_69ca828153f48190bdb27ac46f8e0745 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cafa083fe88190a77efb7cfee4bd6f completed March 30, 2026, 10:32 p.m.
PD Predicate disambiguation batch_69cae91ae008819098e56bbe51143b31 completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 4:41 p.m.