Triple
T33152513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terry Prescott |
E848475
|
entity |
| Predicate | hasEmotionalStruggle |
P115245
|
FINISHED |
| Object | aimlessness |
—
|
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: aimlessness | Statement: [Terry Prescott, hasEmotionalStruggle, aimlessness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmotionalStruggle Context triple: [Terry Prescott, hasEmotionalStruggle, aimlessness]
-
A.
emotionalChallenge
chosen
Indicates a situation where one entity causes or experiences significant emotional difficulty or stress in relation to another entity or circumstance.
-
B.
hasEmotionalIntensity
Indicates that an emotion, experience, or expression is characterized by a particular degree or strength of emotional impact.
-
C.
hasEmotionalDimension
Indicates that something involves, expresses, or affects emotions as a significant aspect of its nature or impact.
-
D.
hasPsychologicalCondition
Indicates that an entity experiences or is diagnosed with a particular psychological or mental health condition.
-
E.
emotionalTrajectory
Indicates how an entity’s emotional state changes or progresses over time in relation to another entity or context.
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:28 a.m.