Triple
T32192422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talky Tina doll |
E822292
|
entity |
| Predicate | directorOfEpisode |
P17519
|
FINISHED |
| Object | Richard C. Sarafian |
—
|
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: Richard C. Sarafian | Statement: [Talky Tina doll, directorOfEpisode, Richard C. Sarafian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorOfEpisode Context triple: [Talky Tina doll, directorOfEpisode, Richard C. Sarafian]
-
A.
episodeDirector
Indicates that one entity serves as the director responsible for the creative and production oversight of a specific episode of a series or show.
-
B.
coWriterOfEpisode
Indicates that one entity collaborated in writing the same episode as the other entity.
-
C.
directedEpisodeOf
chosen
Indicates that a person served as the director for a specific episode of a television or web series.
-
D.
directorOfProduction
Indicates that one entity serves as the director responsible for overseeing the production activities or operations of another entity.
-
E.
director
Indicates that one entity serves as the director (creative or managerial leader) of another entity, such as a film, organization, or project.
- 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_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 1, 2026, 12:35 a.m.