Triple
T15536575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guillermo Vilas |
E370360
|
entity |
| Predicate | yearOfHighestSinglesRanking |
P119076
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [Guillermo Vilas, yearOfHighestSinglesRanking, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfHighestSinglesRanking Context triple: [Guillermo Vilas, yearOfHighestSinglesRanking, 1975]
-
A.
dateOfHighestSinglesRanking
Indicates the specific date on which an entity achieved its highest-ever singles ranking.
-
B.
highestSinglesRanking
Indicates the relationship where a specific singles ranking represents the best (numerically highest) singles position an entity has ever achieved.
-
C.
yearsAsWorldNumberOne
Indicates the number of years an entity held the position of world number one in its field or ranking system.
-
D.
consecutiveWeeksAtWorldNo1
Indicates the number of weeks in a row that an entity has held the world number one ranking.
-
E.
worldNumberOneRankingAchieved
Indicates that an entity has attained the top position in a recognized world ranking within a specific field or domain.
- F. None of above. chosen
Provenance (4 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442f3c688190a599165e526af2ed |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:06 a.m.