Triple
T38679309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toledo Surprise |
E943845
|
entity |
| Predicate | isComedicNumberIn |
P157473
|
FINISHED |
| Object | The Drowsy Chaperone |
—
|
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: The Drowsy Chaperone | Statement: [Toledo Surprise, isComedicNumberIn, The Drowsy Chaperone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isComedicNumberIn Context triple: [Toledo Surprise, isComedicNumberIn, The Drowsy Chaperone]
-
A.
isSilentComedy
Indicates that the work is a comedy in which humor is conveyed without spoken dialogue, relying primarily on visual action and physical expression.
-
B.
isComedyShowOf
Indicates that something is a comedy show that belongs to, features, or is associated with a particular entity (such as a person, group, or channel).
-
C.
hasComedyElements
Indicates that something contains humorous or comedic aspects as part of its overall content or style.
-
D.
isComedySongBy
Indicates that a song belongs to the comedy genre and is performed or created by a specified artist or group.
-
E.
usesInComedy
chosen
Indicates that something is employed or incorporated as a humorous element within a comedic context or performance.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.