Triple
T37591452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jessica Pegula |
E935268
|
entity |
| Predicate | hasCareerHighRankingType |
P50351
|
FINISHED |
| Object | WTA singles ranking |
—
|
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: WTA singles ranking | Statement: [Jessica Pegula, hasCareerHighRankingType, WTA singles ranking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCareerHighRankingType Context triple: [Jessica Pegula, hasCareerHighRankingType, WTA singles ranking]
-
A.
hasRankAtPeakOfCareer
Indicates the specific rank or position an entity held at the highest point of its career.
-
B.
hasWorldRankingPoints
Indicates that an entity possesses a certain number of points in a global or international ranking system.
-
C.
worldNumberOneRankingAchieved
Indicates that an entity has attained the top position in a recognized world ranking within a specific field or domain.
-
D.
highestSinglesRanking
chosen
Indicates the relationship where a specific singles ranking represents the best (numerically highest) singles position an entity has ever achieved.
-
E.
hasEloPeak
Indicates that an entity has achieved a specific highest (peak) Elo rating at some point in time.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
Created at: May 3, 2026, 4:18 p.m.