Triple

T32535752
Position Surface form Disambiguated ID Type / Status
Subject Premier 5 tournaments E831583 entity
Predicate formerNameOfTier P200368 FINISHED
Object WTA 1000 (non-Mandatory) tournaments NE NERFINISHED

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: WTA 1000 (non-Mandatory) tournaments | Statement: [Premier 5 tournaments, formerNameOfTier, WTA 1000 (non-Mandatory) tournaments]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formerNameOfTier
Context triple: [Premier 5 tournaments, formerNameOfTier, WTA 1000 (non-Mandatory) tournaments]
  • A. formerName
    Indicates that an entity was previously known by a different name in the past.
  • B. historicalThirdTierName
    Indicates that an entity previously held a third-tier name or designation in a historical naming or ranking system.
  • C. formerMemberName
    Indicates that the referenced name belongs to an entity that was previously a member of a particular group, organization, or body but is no longer one.
  • D. formerNameOfSeriesCompetedIn
    Indicates that an entity was previously known by a different series name under which it competed.
  • E. formerNameOfRegion
    Indicates that one name was previously used for a region that is now known by a different name.
  • 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_69f34924b1cc8190ad3aca0c0f012a7e completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69ff84df768c81908c65a1a7e33103ad completed May 9, 2026, 7:02 p.m.
PD Predicate disambiguation batch_69ff848d0af881908ee42c27a58af47e completed May 9, 2026, 7:01 p.m.
PDg Predicate description generation batch_69ff84dec2848190b67a497d025c8880 completed May 9, 2026, 7:02 p.m.
Created at: May 1, 2026, 1:01 a.m.