Triple
T2120548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playhouse 90 |
E43909
|
entity |
| Predicate | hasEpisodeFormat |
P20979
|
FINISHED |
| Object | single-play drama |
—
|
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: single-play drama | Statement: [Playhouse 90, hasEpisodeFormat, single-play drama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpisodeFormat Context triple: [Playhouse 90, hasEpisodeFormat, single-play drama]
-
A.
hasEpisodeStructure
chosen
Indicates that one entity defines or possesses the episodic organization, sequencing, or structural pattern of another (such as a series, season, or narrative work).
-
B.
hasEpisode
Indicates that something, typically a series or program, includes a specific episode as one of its constituent parts.
-
C.
hasEP
Indicates that an entity possesses, is associated with, or is characterized by a specific EP (e.g., an endpoint, event point, or designated EP resource) in the given context.
-
D.
broadcastsInFormat
Indicates that a broadcasting entity transmits its content using a specified technical format or standard.
-
E.
includesSpecialEpisodes
Indicates that the subject collection or series contains one or more special, non-regular episodes.
- 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.