Triple
T34410580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rufina Pukhova |
E883249
|
entity |
| Predicate | spouseDefectionContext |
P195946
|
FINISHED |
| Object | Cold War espionage |
—
|
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: Cold War espionage | Statement: [Rufina Pukhova, spouseDefectionContext, Cold War espionage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseDefectionContext Context triple: [Rufina Pukhova, spouseDefectionContext, Cold War espionage]
-
A.
spouseMovement
Indicates a movement or relocation event involving a person and their spouse, such as moving together or one moving to join the other.
-
B.
spouseDivision
Indicates a division or separation between spouses, such as legal, physical, or relational separation within a marital relationship.
-
C.
spouseAction
Indicates that one person performs an action toward or on their spouse within the context of a marital relationship.
-
D.
exSpouse
Indicates that two people were formerly married to each other but are no longer spouses.
-
E.
spouseRelationshipEnd
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
| PDg | Predicate description generation | batch_69fdf5cfa1ec8190b80d887fa1bfb4cf |
completed | May 8, 2026, 2:40 p.m. |
Created at: May 1, 2026, 1:59 a.m.