Triple
T24902657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Cup |
E623620
|
entity |
| Predicate | secondChampionYear |
P105349
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [ATP Cup, secondChampionYear, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondChampionYear Context triple: [ATP Cup, secondChampionYear, 2021]
-
A.
secondSeasonChampionYear
Indicates the year in which an entity won a championship for the second season.
-
B.
secondSeasonChampion
Indicates that the subject is the champion or winner of the second season of a competition, series, or event in relation to the object.
-
C.
secondEditionChampion
chosen
Indicates that an entity is the champion or winner of the second edition or iteration of a particular event, competition, or series.
-
D.
secondWinningSeason
Indicates that the season in question is the second time an entity (such as a team or individual) has achieved a winning record or successful outcome.
-
E.
championshipSeriesRunnerUp
Indicates that an entity finished in second place (as the runner-up) in a specified championship series.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 18, 2026, 5:27 a.m.