Triple

T33221418
Position Surface form Disambiguated ID Type / Status
Subject Trent Tucker Rule E850430 entity
Predicate clockRequirement P176417 FINISHED
Object at least 0.3 seconds to catch and shoot — 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: at least 0.3 seconds to catch and shoot | Statement: [Trent Tucker Rule, clockRequirement, at least 0.3 seconds to catch and shoot]
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: clockRequirement
Context triple: [Trent Tucker Rule, clockRequirement, at least 0.3 seconds to catch and shoot]
  • A. clockInput
    Indicates that one entity serves as a timing or clock signal input that controls or synchronizes the operation of another entity.
  • B. clockType
    Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
  • C. clockShows
    Indicates that a clock displays or presents a particular time or temporal value.
  • D. hasClock
    Indicates that one entity possesses, contains, or is equipped with a clock.
  • E. clockMechanism
    Indicates that one entity functions as the internal mechanism or movement that drives the operation of a clock.
  • 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_69f3496083dc8190b229bb6932dc548b completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6e02ba6b881908dfafc52d3b75f1c completed May 3, 2026, 5:42 a.m.
PD Predicate disambiguation batch_69f6de09c2f481909f8b2545d3208c9f completed May 3, 2026, 5:32 a.m.
PDg Predicate description generation batch_69f6e029f0f88190b1f88d82a4a2cabd completed May 3, 2026, 5:42 a.m.
Created at: May 1, 2026, 1:30 a.m.