Triple
T36135766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimson Lights |
E1045160
|
entity |
| Predicate | broadcastOnNetworkOfWorkAppearedIn |
P17106
|
FINISHED |
| Object | CBS |
—
|
NE NERFINISHED |
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: CBS | Statement: [Crimson Lights, broadcastOnNetworkOfWorkAppearedIn, CBS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastOnNetworkOfWorkAppearedIn Context triple: [Crimson Lights, broadcastOnNetworkOfWorkAppearedIn, CBS]
-
A.
broadcastFor
Indicates that one entity transmits or disseminates content, information, or a signal on behalf of, or in service of, another entity.
-
B.
broadcastAppearance
Indicates that an entity appears or is featured in a broadcast, such as on television, radio, or streaming media.
-
C.
broadcastFrom
Indicates that some content, signal, or message is transmitted or emitted starting at a particular source location, device, or entity.
-
D.
broadcastAfter
Indicates that one broadcast event occurs later in time than another broadcast event.
-
E.
broadcastVia
chosen
Indicates that an action, message, or content is transmitted or disseminated through a specified medium, channel, or platform.
- 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.