Triple
T7674612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullseye |
E173829
|
entity |
| Predicate | hasRebroadcast |
P75116
|
FINISHED |
| Object | reruns on British television channels |
—
|
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: reruns on British television channels | Statement: [Bullseye, hasRebroadcast, reruns on British television channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRebroadcast Context triple: [Bullseye, hasRebroadcast, reruns on British television channels]
-
A.
wasBroadcastOn
Indicates that a media item (such as a program, episode, or event) was transmitted or aired via a particular broadcast channel, station, or network.
-
B.
hasBroadcastContent
Indicates that one entity (typically a broadcast or channel) carries, includes, or transmits the specified content.
-
C.
replayedOn
chosen
Indicates that an event, performance, or recording was played again on a particular medium, platform, or channel.
-
D.
hasBroadcastTime
Indicates that a broadcast (such as a program or transmission) is scheduled or occurs at a specific time.
-
E.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
- 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.