Triple
T25897262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sad-Faced Boy |
E652501
|
entity |
| Predicate | hasTitleCharacterEmotion |
P41794
|
FINISHED |
| Object | sadness |
—
|
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: sadness | Statement: [Sad-Faced Boy, hasTitleCharacterEmotion, sadness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleCharacterEmotion Context triple: [Sad-Faced Boy, hasTitleCharacterEmotion, sadness]
-
A.
hasTitleCharacterTrait
Indicates that a title is associated with a specific character trait of an entity.
-
B.
hasTitleCharacterAction
Indicates that a work’s title explicitly references or is derived from an action performed by a character within that work.
-
C.
hasTypeOfEmotion
chosen
Indicates that an entity experiences, expresses, or is associated with a particular kind or category of emotion.
-
D.
hasTitlePun
Indicates that an entity’s title involves a pun or wordplay, typically combining multiple meanings or sounds for humorous or clever effect.
-
E.
hasTitleCharacterFrom
Indicates that a work has a title that includes or is derived from a specific character.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 22, 2026, 8:23 a.m.