Triple
T24902612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Tour 250 |
E623619
|
entity |
| Predicate | rankingPointsImpact |
P23822
|
FINISHED |
| Object | important for players ranked outside top 20 |
—
|
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: important for players ranked outside top 20 | Statement: [ATP Tour 250, rankingPointsImpact, important for players ranked outside top 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingPointsImpact Context triple: [ATP Tour 250, rankingPointsImpact, important for players ranked outside top 20]
-
A.
rankingImpact
chosen
Indicates how an entity’s position or level in a ranking is affected or influenced by another factor or action.
-
B.
rankingPoints
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
-
C.
rankSignificance
Indicates how important or influential one entity is relative to others within a specified context or ordering.
-
D.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
E.
peakImportance
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
- 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_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 5:27 a.m.