Triple
T25410331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skydeck Plank experience |
E636673
|
entity |
| Predicate | emotionElicited |
P84859
|
FINISHED |
| Object | fear of heights |
—
|
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: fear of heights | Statement: [Skydeck Plank experience, emotionElicited, fear of heights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionElicited Context triple: [Skydeck Plank experience, emotionElicited, fear of heights]
-
A.
emotionEffect
Indicates that one entity’s emotional state causes or influences a change in another entity’s feelings, behavior, or condition.
-
B.
emotionDisplayed
Indicates that an entity is outwardly expressing or showing a particular emotion.
-
C.
emotionState
Indicates the emotional condition or feeling that an entity is currently experiencing.
-
D.
provokesEmotionType
chosen
Indicates that one entity causes or elicits a specific type of emotional response in another entity.
-
E.
emotionDomain
Indicates the general emotional category or type to which a specific emotion belongs (e.g., grouping emotions into broader domains like joy, anger, or fear).
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b00dfbf08190b20120c052126935 |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:53 p.m.