Triple
T24902730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Challenger Tour |
E623622
|
entity |
| Predicate | rankingPointsRange |
P160078
|
FINISHED |
| Object | 50–175 ATP ranking points for tournament winners |
—
|
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: 50–175 ATP ranking points for tournament winners | Statement: [ATP Challenger Tour, rankingPointsRange, 50–175 ATP ranking points for tournament winners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingPointsRange Context triple: [ATP Challenger Tour, rankingPointsRange, 50–175 ATP ranking points for tournament winners]
-
A.
rankingPoints
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
-
B.
rankRange
Indicates that an entity’s rank falls within a specified minimum and maximum range.
-
C.
rankCategoryBetween
Indicates that an entity’s rank or classification falls within a specified range between two rank categories.
-
D.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
E.
rankGrade
Indicates the grade or level assigned to an entity within a ranking or evaluation system.
- 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_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 18, 2026, 5:27 a.m.