Triple

T24705185
Position Surface form Disambiguated ID Type / Status
Subject FIRST Tech Challenge Promote Award E611868 entity
Predicate typicalDurationConstraint P109104 FINISHED
Object short-form video 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-form video | Statement: [FIRST Tech Challenge Promote Award, typicalDurationConstraint, short-form video]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalDurationConstraint
Context triple: [FIRST Tech Challenge Promote Award, typicalDurationConstraint, short-form video]
  • A. typicalDurationDays
    Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
  • B. intendedDuration
    Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
  • C. hasTypicalPerformanceDuration chosen
    Indicates the usual or expected length of time that a performance or activity typically lasts.
  • D. possibleDuration
    Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
  • E. agingTimeMinimum
    Indicates the minimum amount of time that must elapse for something to be considered aged or matured according to a specified standard.
  • 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_69e2c4d9c24c8190a3712d74327f0c6e completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f621fcea1481909b6f8b3af1ee6820 completed May 2, 2026, 4:10 p.m.
PD Predicate disambiguation batch_69f620dc38088190b56b2b15ed75b3c2 completed May 2, 2026, 4:05 p.m.
Created at: April 18, 2026, 3:23 a.m.