Triple
T29112950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anjelika Krylova |
E736961
|
entity |
| Predicate | hasWorldTitle |
P146925
|
FINISHED |
| Object | ice dancing world champion |
—
|
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: ice dancing world champion | Statement: [Anjelika Krylova, hasWorldTitle, ice dancing world champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorldTitle Context triple: [Anjelika Krylova, hasWorldTitle, ice dancing world champion]
-
A.
hasWorldTitleStatus
chosen
Indicates that an entity holds or has been granted the status of a world title or world champion in a particular domain or competition.
-
B.
introducedAsWorldTitleFor
Indicates that one entity was presented or announced as the world title designation for another entity (such as a person, event, or work).
-
C.
hasTitleSystem
Indicates that an entity is associated with, or governed by, a particular title management or titling system.
-
D.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
E.
hasTitleFeature
Indicates that an entity possesses a specific characteristic, attribute, or element related to its title.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 28, 2026, 11:20 a.m.