Triple
T26817720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan Curtis Productions |
E675161
|
entity |
| Predicate | notableTelevisionFilm |
P40639
|
FINISHED |
| Object | The Night Stalker |
—
|
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: The Night Stalker | Statement: [Dan Curtis Productions, notableTelevisionFilm, The Night Stalker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTelevisionFilm Context triple: [Dan Curtis Productions, notableTelevisionFilm, The Night Stalker]
-
A.
notableTelevisionProduction
chosen
Indicates that the subject is significantly associated with the creation or production of the referenced television work.
-
B.
notableSeries
Indicates that an entity is a significant or well-known installment within a particular series or franchise.
-
C.
notableProgramType
Indicates that the subject is recognized for or associated with a particular type or category of program.
-
D.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
-
E.
notableMedia
Indicates a relationship where a media work is recognized as significant, prominent, or especially relevant in connection with a given entity.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: April 27, 2026, 4:53 a.m.