Triple
T6508251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COL |
E150064
|
entity |
| Predicate | usedInDigitalDisplays |
P33608
|
FINISHED |
| Object | score bugs on TV 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: score bugs on TV broadcasts | Statement: [COL, usedInDigitalDisplays, score bugs on TV broadcasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDigitalDisplays Context triple: [COL, usedInDigitalDisplays, score bugs on TV broadcasts]
-
A.
usedInDigitalMedia
chosen
Indicates that something is employed, featured, or incorporated within digital media content or platforms.
-
B.
usedInDigitalCommunication
Indicates that something is employed as a medium, tool, or element within digital or electronic communication processes.
-
C.
displays
Indicates that one entity visually presents or shows another entity’s content or information.
-
D.
usedInECommerce
Indicates that something is employed or applied within the context of electronic commerce activities or systems.
-
E.
scriptUsedInSignage
Indicates that a particular writing system or script is employed in the text or graphics of a sign or signage.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:43 p.m.