Triple
T22370363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vershinin |
E553022
|
entity |
| Predicate | emotionalConnection |
P82444
|
FINISHED |
| Object | Masha Prozorova |
—
|
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: Masha Prozorova | Statement: [Vershinin, emotionalConnection, Masha Prozorova]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionalConnection Context triple: [Vershinin, emotionalConnection, Masha Prozorova]
-
A.
emotionalFocusOf
Indicates that one entity is the primary target or center of another entity’s emotions or emotional attention.
-
B.
emotionallyAttachedTo
Indicates that one entity has a strong emotional bond, affection, or dependence directed toward another entity.
-
C.
emotionalDynamic
Indicates how emotions, moods, or affective states change, interact, or influence each other between entities over time.
-
D.
emotionalCoreOf
Indicates that one entity serves as the central source, essence, or primary driver of another entity’s emotional character or experience.
-
E.
emotionAssociation
chosen
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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15803e7208190ba14c91fb90e15ca |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.