Triple
T12391855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mindy Project |
E296011
|
entity |
| Predicate | subsequentChannelType |
P104711
|
FINISHED |
| Object | streaming television |
—
|
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: streaming television | Statement: [The Mindy Project, subsequentChannelType, streaming television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentChannelType Context triple: [The Mindy Project, subsequentChannelType, streaming television]
-
A.
successorChannel
Indicates that one communication channel directly follows or replaces another in a sequence or progression.
-
B.
subsequentAuthorityType
Indicates the type or category of authority that follows or succeeds a prior authority in a sequence or hierarchy.
-
C.
isSecondaryChannelOf
Indicates that one channel functions as an additional or subordinate channel associated with a primary channel.
-
D.
successorType
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
-
E.
subsequentOperationName
Indicates that one operation occurs later in sequence and is identified by the given subsequent operation name.
- F. None of above. chosen
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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fd0bcc48190bb1a59a3aaa6bfdf |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93fa244148190a960be3ff6f1cf45 |
completed | April 10, 2026, 6:21 p.m. |
Created at: April 8, 2026, 9:54 p.m.