Triple
T9962590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTA 500 tournaments |
E195603
|
entity |
| Predicate | introducedAsCategory |
P44449
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [WTA 500 tournaments, introducedAsCategory, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsCategory Context triple: [WTA 500 tournaments, introducedAsCategory, 2021]
-
A.
introducedCategory
chosen
Indicates that an entity is responsible for bringing a particular category into use, recognition, or existence within a given context.
-
B.
introducedFeatureCategory
Indicates that an entity caused a particular feature category to be created, presented, or made available for the first time.
-
C.
introducedAsModel
Indicates that one entity is presented or identified to others in the role or capacity of a model.
-
D.
introducedAsNameIn
Indicates that an entity is presented or referred to by a particular name within a specified context or source.
-
E.
introducedVia
Indicates that one entity was brought to the attention, presence, or awareness of another entity through a specific intermediary, method, or channel.
- 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.