Triple
T28637062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | This I Cannot Forget |
E724816
|
entity |
| Predicate | hasSpouseAsCentralFigure |
P33561
|
FINISHED |
| Object | Nikolai Bukharin |
—
|
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: Nikolai Bukharin | Statement: [This I Cannot Forget, hasSpouseAsCentralFigure, Nikolai Bukharin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseAsCentralFigure Context triple: [This I Cannot Forget, hasSpouseAsCentralFigure, Nikolai Bukharin]
-
A.
hasSpouseInStory
Indicates that one entity is depicted as the spouse of another within the context of a particular story or narrative.
-
B.
spouseCharacterOf
Indicates a marital relationship where one character is the spouse of another character.
-
C.
spouseAssociatedWith
chosen
Indicates a marital or spousal relationship or close association between two entities.
-
D.
hasPublicFigureSpouse
Indicates that a person’s spouse is a public figure, such as a celebrity, politician, or other widely recognized individual.
-
E.
hasSpousePositionInFamily
Indicates that a person’s spouse holds a specific role or position within the family structure.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 28, 2026, 4:41 a.m.