Triple
T32194415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Still Valley |
E822366
|
entity |
| Predicate | writerTeleplay |
P15305
|
FINISHED |
| Object | Rod Serling |
—
|
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: Rod Serling | Statement: [Still Valley, writerTeleplay, Rod Serling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writerTeleplay Context triple: [Still Valley, writerTeleplay, Rod Serling]
-
A.
screenwriterOfWork
Indicates that a person served as the screenwriter (wrote the screenplay) for a particular creative work.
-
B.
screenwriterInstanceOf
Indicates that a screenwriter belongs to or is classified as a specific type, category, or class of entity.
-
C.
wroteScreenplaysFor
Indicates that one entity is the author or writer of screenplays created for another entity, such as a film, series, or production.
-
D.
screenplayBy
chosen
Indicates that a film, television show, or similar work was written or scripted by a particular person or group.
-
E.
screenwriterOfWorkAppearingIn
Indicates that a person is the screenwriter of a work in which a specified entity (such as a character, actor, or role) appears.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb35e9a08190bb96bb25c32e0812 |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:35 a.m.