Triple
T9962621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTA 500 tournaments |
E195603
|
entity |
| Predicate | previousNameSystem |
P68862
|
FINISHED |
| Object | Premier and International categories |
—
|
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: Premier and International categories | Statement: [WTA 500 tournaments, previousNameSystem, Premier and International categories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNameSystem Context triple: [WTA 500 tournaments, previousNameSystem, Premier and International categories]
-
A.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
B.
formerName
Indicates that an entity was previously known by a different name in the past.
-
C.
previousNamePeriod
Indicates the time span during which an entity was known by a former name before changing to its current name.
-
D.
previousNameOfCountry
Indicates that one country name was formerly used as the official name of another country.
-
E.
replacedEarlierSystems
chosen
Indicates that one system has taken the place of and superseded other systems that existed or were in use before it.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb718cd588190a4aac48220deddec |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.