Triple
T15534723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pink |
E370311
|
entity |
| Predicate | hasPsychologicalEffect |
P39642
|
FINISHED |
| Object | calming |
—
|
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: calming | Statement: [Pink, hasPsychologicalEffect, calming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPsychologicalEffect Context triple: [Pink, hasPsychologicalEffect, calming]
-
A.
hasPharmacologicalEffect
Indicates that one entity produces a specific pharmacological effect or action on another entity.
-
B.
hasPsychologicalCondition
Indicates that an entity experiences or is diagnosed with a particular psychological or mental health condition.
-
C.
hasPsychologicalDepth
Indicates that an entity (such as a work, character, or portrayal) exhibits complex, nuanced inner life, motivations, and emotions that invite deeper psychological interpretation.
-
D.
psychoactiveProfile
chosen
Indicates the characteristic pattern of psychoactive effects or mental state changes produced by a substance, treatment, or exposure.
-
E.
predictedEffect
Indicates that one entity is expected to cause, influence, or result in a particular outcome or consequence for another entity.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.