Triple
T32535648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Britain Wightman Cup team |
E831580
|
entity |
| Predicate | namedAfterCompetition |
P182273
|
FINISHED |
| Object | Wightman Cup |
—
|
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: Wightman Cup | Statement: [Great Britain Wightman Cup team, namedAfterCompetition, Wightman Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterCompetition Context triple: [Great Britain Wightman Cup team, namedAfterCompetition, Wightman Cup]
-
A.
namedAfterCompetitionRenaming
Indicates that an entity received its current name as a result of a renaming process conducted through a competition.
-
B.
namedAfterLeague
Indicates that one entity has been given a name derived from or in honor of a particular league.
-
C.
namedAfterCompetitionFounder
Indicates that something (such as an event, award, or entity) is named in honor of the person who founded the competition.
-
D.
namedAfterTrophy
Indicates that one entity has been given a name derived from or in honor of a particular trophy.
-
E.
laterCompetitionName
Indicates that an entity has its name changed to a different one in a subsequent or later competition.
- 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_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: May 1, 2026, 1:01 a.m.