Triple
T32535955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Ericsson Championships |
E831589
|
entity |
| Predicate | isTitleSponsorNameOf |
P24881
|
FINISHED |
| Object | WTA Finals |
—
|
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 | Statement: [Sony Ericsson Championships, isTitleSponsorNameOf, WTA Finals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTitleSponsorNameOf Context triple: [Sony Ericsson Championships, isTitleSponsorNameOf, WTA Finals]
-
A.
hasTitleSponsor
chosen
Indicates that one entity serves as the primary (title) sponsor for another entity, typically giving its name to the sponsored event, organization, or property.
-
B.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
-
C.
sponsoredNameHolder
Indicates that one entity holds or uses a name or title under the sponsorship or endorsement of another entity.
-
D.
hasSponsor
Indicates that one entity financially or otherwise supports another entity, typically in exchange for recognition or other benefits.
-
E.
hasTitleForFounder
Indicates that a specific title or designation is assigned to a person in their capacity as a founder.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57062c481908b041788842c5990 |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:01 a.m.