Triple
T31418258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenny |
E801456
|
entity |
| Predicate | dramaticToneOfWork |
P21486
|
FINISHED |
| Object | darkly comic |
—
|
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: darkly comic | Statement: [Lenny, dramaticToneOfWork, darkly comic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dramaticToneOfWork Context triple: [Lenny, dramaticToneOfWork, darkly comic]
-
A.
hasDramaticTone
chosen
Indicates that something (such as a work, scene, or expression) is characterized by a heightened, intense, or emotionally charged tone.
-
B.
dramaticFunction
Indicates the role or purpose that something serves within the structure or progression of a dramatic work or narrative.
-
C.
hasDramaticStyle
Indicates that an entity employs or is characterized by a theatrical, emotionally intense, or striking manner of expression or presentation.
-
D.
dramaticCharacter
Indicates that one entity is a character or role that appears within the dramatic work, performance, or narrative represented by the other entity.
-
E.
dramaticRole
Indicates that one entity serves as a character or part played by another entity within a dramatic or theatrical work.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 8:45 p.m.