Triple
T34221262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Rugby Championship |
E877926
|
entity |
| Predicate | rebrandedAsPro14 |
P83848
|
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: [United Rugby Championship, rebrandedAsPro14, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebrandedAsPro14 Context triple: [United Rugby Championship, rebrandedAsPro14, 2017]
-
A.
announcedRebrandingAs
Indicates that one entity has publicly declared it will change its name, brand, or identity to that of another entity.
-
B.
rebrandPeriod
Indicates the time span during which an entity undergoes or is designated for a rebranding.
-
C.
rebrandedYear
chosen
Indicates the year in which an entity changed its brand identity, such as its name, logo, or overall branding.
-
D.
rebrandedByRedBull
Indicates that an entity has undergone a rebranding process carried out by the company Red Bull.
-
E.
rebrandingProgram
Indicates a program or initiative through which an entity changes or updates its brand identity, such as its name, logo, or overall image.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7108232488190a8c33ae6c0246929 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.