Triple
T28670945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madrid Open |
E725715
|
entity |
| Predicate | rankingPointsCategory |
P12314
|
FINISHED |
| Object | Masters 1000 for ATP |
—
|
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: Masters 1000 for ATP | Statement: [Madrid Open, rankingPointsCategory, Masters 1000 for ATP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingPointsCategory Context triple: [Madrid Open, rankingPointsCategory, Masters 1000 for ATP]
-
A.
rankingCategory
Indicates the classification or type of ranking under which an entity is evaluated or ordered.
-
B.
rankingPoints
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
-
C.
hasRankingCategory
chosen
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
-
D.
rankingPointsRange
Indicates the range of ranking points assigned or applicable to an entity within a ranking or scoring system.
-
E.
rankCategoryBetween
Indicates that an entity’s rank or classification falls within a specified range between two rank categories.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 5:03 a.m.