Triple
T36406541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktor Axelsen |
E896761
|
entity |
| Predicate | wasWorldNumberOneInBadmintonMenSingles |
P9283
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Viktor Axelsen, wasWorldNumberOneInBadmintonMenSingles, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasWorldNumberOneInBadmintonMenSingles Context triple: [Viktor Axelsen, wasWorldNumberOneInBadmintonMenSingles, yes]
-
A.
worldNumberOneRankingAchieved
Indicates that an entity has attained the top position in a recognized world ranking within a specific field or domain.
-
B.
formerWorldNo1
chosen
Indicates that the subject was ranked number one in the world in the past, but does not hold that top ranking currently.
-
C.
wasRankedWorldNumberOneUntil
Indicates that an entity held the world number one ranking in a given domain up to, but not beyond, a specified time.
-
D.
men'sSinglesChampion
Indicates that the subject is the winner of the men's singles competition in a given event or tournament.
-
E.
firstMenSinglesAchiever
Indicates that the subject is the first male individual to achieve a particular singles title or milestone.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.