Triple

T24902581
Position Surface form Disambiguated ID Type / Status
Subject ATP Tour 250 E623619 entity
Predicate rankingPointsSinglesFinalist P158135 FINISHED
Object 150 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: 150 | Statement: [ATP Tour 250, rankingPointsSinglesFinalist, 150]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rankingPointsSinglesFinalist
Context triple: [ATP Tour 250, rankingPointsSinglesFinalist, 150]
  • A. rankingPointsSinglesChampion
    Indicates the number of ranking points awarded to an entity for winning a singles championship.
  • B. grandSlamFinalistInSingles
    Indicates that a person has reached the final round of a Grand Slam tennis tournament in singles competition.
  • C. grandSlamSinglesFinalResult
    Indicates the outcome of a Grand Slam tennis singles final match between competitors, typically specifying the winner, loser, and possibly the score.
  • D. highestSinglesRanking
    Indicates the relationship where a specific singles ranking represents the best (numerically highest) singles position an entity has ever achieved.
  • E. grandSlamSinglesFinalOpponent
    Indicates that one person was the opposing player faced by another person in the final match of a Grand Slam singles tennis tournament.
  • 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_69f464b4c9b0819085daa00c7c3b8b76 completed May 1, 2026, 8:30 a.m.
PD Predicate disambiguation batch_69f45cf017a88190b4985b11159c907d completed May 1, 2026, 7:57 a.m.
PDg Predicate description generation batch_69f464ae42e88190b3549fdf4e0b425e completed May 1, 2026, 8:30 a.m.
Created at: April 18, 2026, 5:27 a.m.