Triple
T14077870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirsty (Intimacy) |
E338785
|
entity |
| Predicate | emotionalCharacteristics |
P87208
|
FINISHED |
| Object | emotionally complex |
—
|
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: emotionally complex | Statement: [Kirsty (Intimacy), emotionalCharacteristics, emotionally complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionalCharacteristics Context triple: [Kirsty (Intimacy), emotionalCharacteristics, emotionally complex]
-
A.
emotionalTrait
chosen
Indicates that an entity possesses a particular emotional characteristic, disposition, or affective quality.
-
B.
emotionalDynamic
Indicates how emotions, moods, or affective states change, interact, or influence each other between entities over time.
-
C.
emotionalCoreOf
Indicates that one entity serves as the central source, essence, or primary driver of another entity’s emotional character or experience.
-
D.
emotionalTrajectory
Indicates how an entity’s emotional state changes or progresses over time in relation to another entity or context.
-
E.
emotionAssociation
Indicates an emotional relationship or connection that one entity has toward another entity or concept.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5e027881908f610f5bab7598d4 |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.