Triple
T28549521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anton Sikharulidze |
E722841
|
entity |
| Predicate | formerPartnerInSport |
P61701
|
FINISHED |
| Object | Elena Berezhnaya |
—
|
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: Elena Berezhnaya | Statement: [Anton Sikharulidze, formerPartnerInSport, Elena Berezhnaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerPartnerInSport Context triple: [Anton Sikharulidze, formerPartnerInSport, Elena Berezhnaya]
-
A.
formerPartner
Indicates that one entity was previously in a romantic or partnership relationship with another entity, but that relationship has since ended.
-
B.
formerPartnerClub
Indicates that a club previously had a partnership or formal association with another club, but that relationship has since ended.
-
C.
formerAthlete
Indicates that a person previously had the role or status of an athlete but no longer does.
-
D.
partnerInCompetition
Indicates that two or more entities are collaborating as partners or teammates within the same competitive event or context.
-
E.
hasPartnerInSport
chosen
Indicates that one entity has another entity as a partner with whom they jointly participate in a sport or sporting activity.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: April 28, 2026, 3:41 a.m.