Triple
T10961291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hennessy Gold Cup |
E258978
|
entity |
| Predicate | sponsorshipChangeYear |
P82079
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Hennessy Gold Cup, sponsorshipChangeYear, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorshipChangeYear Context triple: [Hennessy Gold Cup, sponsorshipChangeYear, 2017]
-
A.
sponsorshipRenamedFrom
Indicates that a sponsorship currently known by one name previously existed under a different, earlier name.
-
B.
namingRightsChangeYear
chosen
Indicates the year in which the naming rights for something (such as a venue, event, or asset) were changed from one name or sponsor to another.
-
C.
sponsorshipEnded
Indicates that a previously existing sponsorship relationship between entities has been terminated or has come to an end.
-
D.
sponsorshipEndedWith
Indicates that a previously existing sponsorship relationship between entities has come to an end.
-
E.
renamingSponsor
Indicates that one entity serves as the sponsor responsible for the renaming of another entity.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7712bf65c8190b847784d885876fd |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.