Triple
T35707183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shingo Kunieda |
E1031749
|
entity |
| Predicate | worldNo1WeeksSingles |
P103691
|
FINISHED |
| Object | over 500 weeks |
—
|
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: over 500 weeks | Statement: [Shingo Kunieda, worldNo1WeeksSingles, over 500 weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldNo1WeeksSingles Context triple: [Shingo Kunieda, worldNo1WeeksSingles, over 500 weeks]
-
A.
formerWorldNo1
Indicates that the subject was ranked number one in the world in the past, but does not hold that top ranking currently.
-
B.
highestSinglesRanking
Indicates the relationship where a specific singles ranking represents the best (numerically highest) singles position an entity has ever achieved.
-
C.
worldNumberOneRankingAchieved
chosen
Indicates that an entity has attained the top position in a recognized world ranking within a specific field or domain.
-
D.
men'sSinglesChampion
Indicates that the subject is the winner of the men's singles competition in a given event or tournament.
-
E.
wonWimbledonSingles
Indicates that an entity has won the Wimbledon tennis tournament in the singles category.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 3, 2026, 4:05 p.m.