Triple
T2120539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playhouse 90 |
E43909
|
entity |
| Predicate | episodeType |
P20471
|
FINISHED |
| Object | standalone teleplays |
—
|
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: standalone teleplays | Statement: [Playhouse 90, episodeType, standalone teleplays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: episodeType Context triple: [Playhouse 90, episodeType, standalone teleplays]
-
A.
televisionShow
Indicates that one entity is a television show associated with, or featured in relation to, another entity.
-
B.
directedEpisodeOf
Indicates that a person served as the director for a specific episode of a television or web series.
-
C.
notableProgramType
chosen
Indicates that the subject is recognized for or associated with a particular type or category of program.
-
D.
hasEpisodeStructure
Indicates that one entity defines or possesses the episodic organization, sequencing, or structural pattern of another (such as a series, season, or narrative work).
-
E.
entertainmentType
Indicates the kind or category of entertainment associated with an entity or event.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb3404348190bc843022fbd2b4d0 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.