Triple
T28768527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oksana Grishuk |
E726343
|
entity |
| Predicate | wonWithPartner |
P82424
|
FINISHED |
| Object | Evgeni Platov |
—
|
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: Evgeni Platov | Statement: [Oksana Grishuk, wonWithPartner, Evgeni Platov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonWithPartner Context triple: [Oksana Grishuk, wonWithPartner, Evgeni Platov]
-
A.
winnerPairs
chosen
Indicates that the paired entities are jointly identified as winners or form a winning combination in a given context.
-
B.
winnerProfessionalPartner
Indicates that one entity is the professional partner of the winning participant in a competition or contest.
-
C.
hasDoublesPartner
Indicates that one entity serves as the doubles partner of another in a paired or team-based activity or sport.
-
D.
wonFor
Indicates that one entity received an award, prize, or recognition specifically on behalf of or representing another entity.
-
E.
wonBy
Indicates that a contest, game, or competition is decided in favor of a particular participant or side.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:14 a.m.