Triple
T28722319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTA Tour |
E730127
|
entity |
| Predicate | hasSeasonHighlight |
P31151
|
FINISHED |
| Object | WTA Finals year-end championship |
—
|
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 Finals year-end championship | Statement: [WTA Tour, hasSeasonHighlight, WTA Finals year-end championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonHighlight Context triple: [WTA Tour, hasSeasonHighlight, WTA Finals year-end championship]
-
A.
hasSeasonalHighlight
chosen
Indicates that something features a notable or emphasized aspect during a particular season or time of year.
-
B.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
C.
hasSeasonTheme
Indicates that something is associated with or characterized by a particular seasonal theme.
-
D.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
E.
notableSeason
Indicates that a particular season is especially significant or noteworthy in relation to an entity (such as a person, team, or series).
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 28, 2026, 5:54 a.m.