Triple

T38082576
Position Surface form Disambiguated ID Type / Status
Subject NBA steals E950892 entity
Predicate cannotOccurWhen P171016 FINISHED
Object defender commits a foul on the play 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: defender commits a foul on the play | Statement: [NBA steals, cannotOccurWhen, defender commits a foul on the play]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cannotOccurWhen
Context triple: [NBA steals, cannotOccurWhen, defender commits a foul on the play]
  • A. notValidWhen
    Indicates that a condition, state, or action is invalid or not applicable whenever a specified circumstance or condition holds.
  • B. occursWhen
    Indicates that one event or condition happens at the same time or is triggered under the circumstances defined by another event or condition.
  • C. occursWithout
    Indicates that one event or condition happens in the absence of another specified event or condition.
  • D. cannotBeUsedAs
    Indicates that one entity is not permitted or not suitable to serve the role, function, or purpose of another entity.
  • E. cannotRunIf chosen
    Indicates that one action, process, or condition is not allowed to execute or occur whenever another specified action, process, or condition is present or active.
  • 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_69f76f03a3608190a73fd6df87c792a8 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fd37b695c88190855801626f91c4cd completed May 8, 2026, 1:09 a.m.
PD Predicate disambiguation batch_69fd374cccf08190a230e87164af5938 completed May 8, 2026, 1:07 a.m.
Created at: May 3, 2026, 4:21 p.m.