Triple
T21525016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resorts World Arena |
E531070
|
entity |
| Predicate | sponsorshipRenaming |
P119655
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Resorts World Arena, sponsorshipRenaming, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorshipRenaming Context triple: [Resorts World Arena, sponsorshipRenaming, 2018]
-
A.
renamingSponsor
Indicates that one entity serves as the sponsor responsible for the renaming of another entity.
-
B.
sponsorshipRenamedFrom
Indicates that a sponsorship currently known by one name previously existed under a different, earlier name.
-
C.
renamedAfterSponsorship
chosen
Indicates that an entity’s name was changed as a result of a sponsorship agreement or sponsorship-related naming rights.
-
D.
sponsorshipChangeTo
Indicates a change in sponsorship where an entity becomes the new sponsor of another entity, replacing or updating the previous sponsorship arrangement.
-
E.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee885073888190ae49f967f72acbf8 |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.