Triple
T34410579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rufina Pukhova |
E883249
|
entity |
| Predicate | spouseDefectionDestination |
P158167
|
FINISHED |
| Object | Soviet Union |
—
|
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: Soviet Union | Statement: [Rufina Pukhova, spouseDefectionDestination, Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseDefectionDestination Context triple: [Rufina Pukhova, spouseDefectionDestination, Soviet Union]
-
A.
residenceAfterDefection
chosen
Indicates that an entity’s place of residence is located in or associated with another entity after the entity has defected from a previous affiliation or location.
-
B.
spouseTravelDestination
Indicates that a location is the place where a person’s spouse is traveling or intends to travel.
-
C.
spouseMovement
Indicates a movement or relocation event involving a person and their spouse, such as moving together or one moving to join the other.
-
D.
spouseCountryOfCitizenship
Indicates the country in which a person's spouse holds legal citizenship.
-
E.
spouseLaterNationality
Indicates that a person’s spouse held or acquired a particular nationality at a later point in time than the reference period.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 1, 2026, 1:59 a.m.