Triple
T28015005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ineos Grenadiers |
E707523
|
entity |
| Predicate | titleSponsorChangeYear |
P82079
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Ineos Grenadiers, titleSponsorChangeYear, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleSponsorChangeYear Context triple: [Ineos Grenadiers, titleSponsorChangeYear, 2019]
-
A.
sponsorshipChangeTo
Indicates a change in sponsorship where an entity becomes the new sponsor of another entity, replacing or updating the previous sponsorship arrangement.
-
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.
renamingSponsor
Indicates that one entity serves as the sponsor responsible for the renaming of another entity.
-
D.
renamedYear
Indicates the year in which an entity underwent a renaming or change of name.
-
E.
firstYearTitleSponsor
Indicates that the entity served as the title sponsor for the first year of a particular event, program, or competition.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 27, 2026, 8:06 p.m.