Triple
T15752883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seth Brundle |
E381890
|
entity |
| Predicate | mentalStateChange |
P120499
|
FINISHED |
| Object | increasing instability |
—
|
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: increasing instability | Statement: [Seth Brundle, mentalStateChange, increasing instability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentalStateChange Context triple: [Seth Brundle, mentalStateChange, increasing instability]
-
A.
emotionState
Indicates the emotional condition or feeling that an entity is currently experiencing.
-
B.
moodShiftFromPreviousChapter
Indicates a change in emotional tone or atmosphere compared to the immediately preceding chapter.
-
C.
emotionEffect
Indicates that one entity’s emotional state causes or influences a change in another entity’s feelings, behavior, or condition.
-
D.
feltIn
Indicates that a sensation, emotion, or effect is experienced within a particular location, context, or entity.
-
E.
emotionalChallenge
Indicates a situation where one entity causes or experiences significant emotional difficulty or stress in relation to another entity or circumstance.
- F. None of above. chosen
Provenance (4 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0b4d01c9c81909f6b611e8144c838 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 10, 2026, 4:47 a.m.