Triple
T23802158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomas Berdych |
E588701
|
entity |
| Predicate | achievedHighestSinglesRankingOn |
P50352
|
FINISHED |
| Object | 2015-05-18 |
—
|
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: 2015-05-18 | Statement: [Tomas Berdych, achievedHighestSinglesRankingOn, 2015-05-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedHighestSinglesRankingOn Context triple: [Tomas Berdych, achievedHighestSinglesRankingOn, 2015-05-18]
-
A.
dateOfHighestSinglesRanking
chosen
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.
yearOfHighestSinglesRanking
Indicates the specific year in which an entity achieved its highest-ever singles ranking.
-
D.
wasRankedWorldNumberOneUntil
Indicates that an entity held the world number one ranking in a given domain up to, but not beyond, a specified time.
-
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.
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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c74e430481909debd10c71785912 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:53 p.m.