Triple
T36412443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sometimes I Think About Dying |
E896915
|
entity |
| Predicate | featuresProtagonistWithTrait |
P21469
|
FINISHED |
| Object | social anxiety |
—
|
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: social anxiety | Statement: [Sometimes I Think About Dying, featuresProtagonistWithTrait, social anxiety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresProtagonistWithTrait Context triple: [Sometimes I Think About Dying, featuresProtagonistWithTrait, social anxiety]
-
A.
protagonistCharacteristic
chosen
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
B.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
C.
hasSupportingCharacterTrait
Indicates that a supporting character possesses a particular trait, quality, or characteristic.
-
D.
featuresProtagonistOccupation
Indicates that the work’s main character has a specified occupation or job role.
-
E.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.