Triple
T33416059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Box |
E855718
|
entity |
| Predicate | includedInProgram |
P36500
|
FINISHED |
| Object | Welcome to the Blumhouse film series |
E2049261
|
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: Welcome to the Blumhouse film series | Statement: [Black Box, includedInProgram, Welcome to the Blumhouse film series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInProgram Context triple: [Black Box, includedInProgram, Welcome to the Blumhouse film series]
-
A.
programIncluded
chosen
Indicates that a particular program is contained within, or forms part of, another specified collection, package, or set of programs.
-
B.
subjectToProgram
Indicates that an entity is governed, regulated, or affected by a specific program, policy, or systematic initiative.
-
C.
contributedToProgram
Indicates that an entity played a role in creating, supporting, or participating in a particular program.
-
D.
isProgrammedIn
Indicates that a software system, application, or component is implemented using a particular programming language.
-
E.
mayIncludeProgram
Indicates that something is permitted to contain or encompass a particular program as part of its composition or configuration.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a03173dd4988190a38175b63cba9f09 |
completed | May 12, 2026, 12:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35814d53288190bdacb516eb3b6d29 |
completed | June 19, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_6a031700ade88190afd217d5966b03b4 |
completed | May 12, 2026, 12:03 p.m. |
Created at: May 1, 2026, 1:36 a.m.