Triple

T2811083
Position Surface form Disambiguated ID Type / Status
Subject LAK E54170 entity
Predicate usedOnScoreBug P36395 FINISHED
Object television NBA broadcasts 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: television NBA broadcasts | Statement: [LAK, usedOnScoreBug, television NBA broadcasts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedOnScoreBug
Context triple: [LAK, usedOnScoreBug, television NBA broadcasts]
  • A. usedOnScoreboards
    Indicates that something is employed or displayed specifically on scoreboards.
  • B. scoreUsedFor
    Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
  • C. usedInScoreGraphics chosen
    Indicates that something (such as a technique, element, or resource) is employed within the creation or presentation of score graphics.
  • D. isScoreFor
    Indicates that one value represents the score or result associated with a particular entity, event, or performance.
  • E. scoreReportedTo
    Indicates that a score or result has been communicated or submitted from one party to another.
  • 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_69ab49dcee188190b5c6eca9ae9e3469 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abde354a5881908cd3d545f7dda81c completed March 7, 2026, 8:13 a.m.
PD Predicate disambiguation batch_69abdd0740208190911dc9c9546a79ae completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 9:59 p.m.