Triple
T24902552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Tour Masters 1000 |
E623618
|
entity |
| Predicate | typeOfRankingPoints |
P164765
|
FINISHED |
| Object | ATP singles ranking points |
—
|
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 singles ranking points | Statement: [ATP Tour Masters 1000, typeOfRankingPoints, ATP singles ranking points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRankingPoints Context triple: [ATP Tour Masters 1000, typeOfRankingPoints, ATP singles ranking points]
-
A.
typeOfRankingEvent
Indicates the specific kind or category of ranking-related event that is being referred to.
-
B.
rankingPoints
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
-
C.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
-
D.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
E.
hasRankingCategory
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification 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_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 18, 2026, 5:27 a.m.