Triple
T30925743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sexual Harassment (The Office U.S.) |
E787849
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | The Office (U.S. TV series) episode |
C2046
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: The Office (U.S. TV series) episode Context triple: [Sexual Harassment (The Office U.S.), instanceOf, The Office (U.S. TV series) episode]
-
A.
television episode
chosen
A television episode is a single, self-contained installment of a television series that contributes to an ongoing narrative or theme and is typically broadcast or streamed as part of a scheduled sequence.
-
B.
Regular Show episode
A Regular Show episode is a single installment of the animated television series "Regular Show," typically following Mordecai, Rigby, and their coworkers as a mundane task spirals into surreal, often supernatural chaos.
-
C.
The Orville episode
A specific installment of the science fiction television series "The Orville," consisting of a self-contained narrative (often with ongoing character and plot development) that airs as part of the show's episodic run.
-
D.
Torchwood episode
A Torchwood episode is a single installment of the British science fiction television series "Torchwood," typically featuring a self-contained or arc-related story about the Torchwood Institute investigating alien phenomena and supernatural events.
-
E.
television comedy
A television comedy is a scripted TV program designed primarily to entertain through humor, often featuring recurring characters, situational conflicts, and comedic dialogue or scenarios.
- F. None of above.
Provenance (1 batch)
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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:51 p.m.