Triple
T24902582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Tour 250 |
E623619
|
entity |
| Predicate | rankingPointsSinglesSemifinalist |
P158688
|
FINISHED |
| Object | 90 |
—
|
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: 90 | Statement: [ATP Tour 250, rankingPointsSinglesSemifinalist, 90]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingPointsSinglesSemifinalist Context triple: [ATP Tour 250, rankingPointsSinglesSemifinalist, 90]
-
A.
rankingPointsSinglesFinalist
Indicates the number of ranking points awarded to a player for reaching the final (but not necessarily winning) in a singles competition.
-
B.
rankingPointsSinglesChampion
Indicates the number of ranking points awarded to an entity for winning a singles championship.
-
C.
grandSlamSinglesSemifinal
Indicates that an entity reached or participated in the semifinal round of a Grand Slam tennis singles tournament.
-
D.
reachedSemiFinalOf
Indicates that an entity progressed far enough in a competition or tournament to participate in its semi-final round.
-
E.
semifinalMatchup
Indicates that two competitors or teams are paired to compete against each other in a semifinal round of a tournament or competition.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f47b7f657c81908174590c811a3cbf |
completed | May 1, 2026, 10:07 a.m. |
Created at: April 18, 2026, 5:27 a.m.