Triple

T16186057
Position Surface form Disambiguated ID Type / Status
Subject Lucas Oil Knoxville Championship Cup Series E392804 entity
Predicate timingAndScoring P47077 FINISHED
Object electronic timing system 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: electronic timing system | Statement: [Lucas Oil Knoxville Championship Cup Series, timingAndScoring, electronic timing system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timingAndScoring
Context triple: [Lucas Oil Knoxville Championship Cup Series, timingAndScoring, electronic timing system]
  • A. decidingScoreTime
    Indicates the point in time at which a decisive or game-determining score occurs.
  • B. competitionTiming
    Indicates the temporal relationship or scheduling of when a competition or competitive event takes place.
  • C. timingOfRace chosen
    Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
  • D. scoring
    Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
  • E. timingPartner
    Indicates that one entity serves as a temporal counterpart or reference point for another, aligning their actions or events in 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_69d87f1e49ac8190a311b54d32990576 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e22061f47481909ededd5eed40f5a4 completed April 17, 2026, 11:58 a.m.
PD Predicate disambiguation batch_69e219e11f6081909106b1240a17fd37 completed April 17, 2026, 11:30 a.m.
Created at: April 10, 2026, 5:02 a.m.