Triple
T25531906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isaeva (first husband) |
E639940
|
entity |
| Predicate | spouseOfPersonWhoLaterMarried |
P139882
|
FINISHED |
| Object | Fyodor Dostoevsky |
—
|
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: Fyodor Dostoevsky | Statement: [Isaeva (first husband), spouseOfPersonWhoLaterMarried, Fyodor Dostoevsky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfPersonWhoLaterMarried Context triple: [Isaeva (first husband), spouseOfPersonWhoLaterMarried, Fyodor Dostoevsky]
-
A.
spouseLaterMarriedBy
Indicates that one’s spouse subsequently entered into a later marriage with another partner.
-
B.
subsequentSpouse
chosen
Indicates that one person is a later spouse of another, following a previous marriage involving at least one of them.
-
C.
fiancéeLaterMarried
Indicates that a person who was once engaged to another person later went on to marry that same individual.
-
D.
spouseOfFormer
Indicates that one entity is the spouse of another entity who is a former holder of some role, status, or position.
-
E.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 3:14 p.m.