Triple
T24902611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Tour 250 |
E623619
|
entity |
| Predicate | tourLevelComparedToATPFinals |
P157880
|
FINISHED |
| Object | below |
—
|
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: below | Statement: [ATP Tour 250, tourLevelComparedToATPFinals, below]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourLevelComparedToATPFinals Context triple: [ATP Tour 250, tourLevelComparedToATPFinals, below]
-
A.
tourLevelComparedToGrandSlams
Indicates how the competitive or organizational level of a given tennis tour or tournament compares relative to the Grand Slam tournaments.
-
B.
tierRelativeToATP1000
Indicates the relative ranking or tier of something when compared to the ATP 1000 tournament level.
-
C.
ATPFinalsReachedSingles
Indicates that a player has reached (but not necessarily won) the singles final of the ATP Finals tournament.
-
D.
tierRelativeToATP250
chosen
Indicates the relative competitive or organizational level of an event or entity compared to the ATP 250 tournament tier.
-
E.
ATPtourLevelTitles
Indicates the number of ATP Tour–level tournament titles a player has won.
- 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_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:27 a.m.