Triple
T34641587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libria |
E889572
|
entity |
| Predicate | enforcesEmotionSuppressionWith |
P91075
|
FINISHED |
| Object | drug Prozium |
—
|
NE NERFINISHED |
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: drug Prozium | Statement: [Libria, enforcesEmotionSuppressionWith, drug Prozium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcesEmotionSuppressionWith Context triple: [Libria, enforcesEmotionSuppressionWith, drug Prozium]
-
A.
requiresEmotion
Indicates that one entity’s occurrence, validity, or performance depends on the presence or experience of a particular emotion in another entity.
-
B.
hasEmotionSimulation
Indicates that an entity is capable of generating or exhibiting a simulated emotional state rather than a genuine one.
-
C.
expressesEmotionThrough
Indicates that one entity conveys or manifests an emotion by means of another entity (such as an action, medium, or expression).
-
D.
hasEmotionalDimension
Indicates that something involves, expresses, or affects emotions as a significant aspect of its nature or impact.
-
E.
suppressedIn
chosen
Indicates that one entity’s presence, activity, or expression is reduced, inhibited, or prevented by another entity or condition.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:04 a.m.