Triple

T30933597
Position Surface form Disambiguated ID Type / Status
Subject Kevin's Famous Chili E788058 entity
Predicate hasRunningTimeContext P74363 FINISHED
Object short cold-open sequence 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: short cold-open sequence | Statement: [Kevin's Famous Chili, hasRunningTimeContext, short cold-open sequence]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRunningTimeContext
Context triple: [Kevin's Famous Chili, hasRunningTimeContext, short cold-open sequence]
  • A. hasRunningTimeCategory chosen
    Indicates that an entity is associated with a specific category based on its running time or duration.
  • B. hasTimeStart
    Indicates that an event, process, or state begins at a specific point in time.
  • C. hasPerformanceContext
    Indicates that an entity is associated with a specific performance-related situation, setting, or set of conditions under which it operates or is evaluated.
  • D. hasTimingCapability
    Indicates that an entity possesses the ability to measure, control, or manage timing-related aspects of an operation or process.
  • E. hasDurationCharacteristic
    Indicates that something possesses a specific temporal property, such as length, span, or persistence over time.
  • 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_69f224c0b7fc819090cb89df60d23653 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6cee45590819086e489bfccbe4ac3 completed May 3, 2026, 4:28 a.m.
PD Predicate disambiguation batch_69f6cc1188708190b8f0f56e595e6057 completed May 3, 2026, 4:16 a.m.
Created at: April 29, 2026, 8:52 p.m.