Triple
T15200761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denis Shapovalov |
E363260
|
entity |
| Predicate | hasWonTitleLevel |
P73147
|
FINISHED |
| Object | ATP Tour singles title |
—
|
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: ATP Tour singles title | Statement: [Denis Shapovalov, hasWonTitleLevel, ATP Tour singles title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWonTitleLevel Context triple: [Denis Shapovalov, hasWonTitleLevel, ATP Tour singles title]
-
A.
hasWonTitleType
chosen
Indicates that an entity has won a title of a specified type.
-
B.
hasWonRegionalTitle
Indicates that an entity has achieved victory in a competition at the regional level and been awarded the corresponding title.
-
C.
hasAwardLevel
Indicates that an entity possesses or has been assigned a specific level, tier, or rank within an award or recognition system.
-
D.
wonTitleFrom
Indicates that one entity obtained a title or championship by defeating or surpassing another specific entity who previously held it.
-
E.
wonTitleWith
Indicates that an entity secured a specific title, award, or championship while being associated with or representing another entity (such as a team, organization, or group).
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b588b88190a88e91d521acbdfe |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:10 a.m.