Triple
T20295262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joey Boca |
E505330
|
entity |
| Predicate | toneOfStoryInvolving |
P130432
|
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: [Joey Boca, toneOfStoryInvolving, darkly comic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toneOfStoryInvolving Context triple: [Joey Boca, toneOfStoryInvolving, darkly comic]
-
A.
tone
Indicates the characteristic attitude or emotional quality expressed in how something is communicated or presented.
-
B.
contributesToTone
Indicates that one entity plays a role in shaping, influencing, or determining the overall tone or mood of another entity.
-
C.
hasNarrativeToneOfWork
chosen
Indicates that a work exhibits or is characterized by a particular narrative tone.
-
D.
inTonality
Indicates that something (such as a musical element, passage, or piece) is expressed, structured, or interpreted within a specific musical key or tonal framework.
-
E.
toneOfCharacterArc
Indicates the overall emotional or thematic quality that characterizes how a character’s arc unfolds over the course of a story.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6770714c4819080e3256325747ebf |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:15 a.m.