Triple
T24902697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Rankings |
E623621
|
entity |
| Predicate | usesPointsScale |
P64949
|
FINISHED |
| Object | tournament category-based 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: tournament category-based points | Statement: [ATP Rankings, usesPointsScale, tournament category-based points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPointsScale Context triple: [ATP Rankings, usesPointsScale, tournament category-based points]
-
A.
distanceScaleUse
Indicates that one entity uses or applies the distance scale defined or provided by another entity.
-
B.
usesPointsForDraw
Indicates that an entity relies on or applies a points-based system to determine or execute a draw (such as a lottery, selection, or outcome).
-
C.
usesPointsSystem
chosen
Indicates that an entity operates or functions based on a structured points-based system for evaluation, rewards, or progression.
-
D.
userScale
Indicates that a user adjusts or sets the scale, size, or zoom level of an object, interface, or content.
-
E.
usesScaleDegrees
Indicates that something is expressed, analyzed, or organized in terms of musical scale degrees rather than absolute pitches.
- 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_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:27 a.m.