Triple
T35970518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strelnikov |
E1040271
|
entity |
| Predicate | spouseOfInRealName |
P109531
|
FINISHED |
| Object | Tonia Gromeko |
—
|
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: Tonia Gromeko | Statement: [Strelnikov, spouseOfInRealName, Tonia Gromeko]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfInRealName Context triple: [Strelnikov, spouseOfInRealName, Tonia Gromeko]
-
A.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
B.
spouseOfWork
Indicates that one person is the spouse of another specifically in the context of their workplace or professional environment.
-
C.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
D.
spousePersonalName
chosen
Indicates the personal name of a person’s spouse in the relationship.
-
E.
spouseAlsoKnownAs
Indicates that a person’s spouse is referred to by an alternative name or alias.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:07 p.m.