Triple
T12346338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Robert "Bob" Hartley |
E294363
|
entity |
| Predicate | notableEpisodeDevice |
P104590
|
FINISHED |
| Object | therapy sessions used for comedy |
—
|
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: therapy sessions used for comedy | Statement: [Dr. Robert "Bob" Hartley, notableEpisodeDevice, therapy sessions used for comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEpisodeDevice Context triple: [Dr. Robert "Bob" Hartley, notableEpisodeDevice, therapy sessions used for comedy]
-
A.
notableEpisode
Indicates that a particular episode is especially significant, memorable, or noteworthy in relation to the subject.
-
B.
notableEP
Indicates that an entity is especially well-known or significant for a particular EP (extended play recording).
-
C.
notableEpisodeCount
Indicates the number of episodes in which the subject is notably featured or recognized.
-
D.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
-
E.
associatedEpisode
Indicates that one entity is linked or connected to a particular episode as its related or relevant installment.
- F. None of above. chosen
Provenance (4 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7a4a448190aa70d66dc2f406c1 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:53 p.m.