Triple
T34580912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natalia Shaposhnikova |
E887897
|
entity |
| Predicate | hasEponymousSkillOn |
P57442
|
FINISHED |
| Object | uneven bars |
—
|
LITERAL FINISHED |
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: uneven bars | Statement: [Natalia Shaposhnikova, hasEponymousSkillOn, uneven bars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEponymousSkillOn Context triple: [Natalia Shaposhnikova, hasEponymousSkillOn, uneven bars]
-
A.
hasEponymousSkill
chosen
Indicates that an entity possesses a skill that is named after a particular person or entity.
-
B.
indicatesSkill
Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another entity.
-
C.
killsAt
Indicates that one entity causes the death of another entity at a specific time or event.
-
D.
hasSkillTree
Indicates that an entity is associated with a structured progression of skills or abilities, typically organized in a branching or hierarchical form.
-
E.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720c32a60819083bd47b9b1903ebc |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.