Triple

T24971073
Position Surface form Disambiguated ID Type / Status
Subject ATP 500 E624890 entity
Predicate rankingPointsForSinglesChampion P157861 FINISHED
Object 500 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: 500 | Statement: [ATP 500, rankingPointsForSinglesChampion, 500]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rankingPointsForSinglesChampion
Context triple: [ATP 500, rankingPointsForSinglesChampion, 500]
  • A. rankingPointsSinglesChampion chosen
    Indicates the number of ranking points awarded to an entity for winning a singles championship.
  • B. rankingPointsSinglesFinalist
    Indicates the number of ranking points awarded to a player for reaching the final (but not necessarily winning) in a singles competition.
  • C. rankingPointsSinglesQuarterfinalist
    Indicates that an entity receives or is associated with ranking points specifically for reaching the singles quarterfinal round in a competition or tournament.
  • D. rankingPointsSinglesSemifinalist
    Indicates that an entity receives ranking points for reaching the semifinals in a singles competition.
  • E. highestSinglesRanking
    Indicates the relationship where a specific singles ranking represents the best (numerically highest) singles position an entity has ever achieved.
  • 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_69e2ff24512481908e9a72315b8d0354 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f621fcea1481909b6f8b3af1ee6820 completed May 2, 2026, 4:10 p.m.
PD Predicate disambiguation batch_69f620dc38088190b56b2b15ed75b3c2 completed May 2, 2026, 4:05 p.m.
Created at: April 18, 2026, 6:01 a.m.