Triple
T34882547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bizarre |
E1006053
|
entity |
| Predicate | originalNetworkInUnitedStates |
P44876
|
FINISHED |
| Object | Showtime |
E71141
|
NE 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: Showtime | Statement: [Bizarre, originalNetworkInUnitedStates, Showtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNetworkInUnitedStates Context triple: [Bizarre, originalNetworkInUnitedStates, Showtime]
-
A.
hasNetworkUS
Indicates that an entity possesses, operates, or is associated with a network located in or serving the United States.
-
B.
originalNetwork
Indicates that one entity is the original or source network from which another network or derived entity is based or obtained.
-
C.
originalChannelInUS
chosen
Indicates that the entity was originally broadcast or distributed on a specific television or media channel in the United States.
-
D.
originalNetworkName
Indicates the name of the network from which something (e.g., data, content, or a connection) originally came.
-
E.
hasNetworkOfOrigin
Indicates that an entity originates from, or is primarily associated with, a particular network or source network.
- F. None of above.
Provenance (4 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a8a81a5c81909c635685e158f869 |
completed | June 21, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.