Triple
T1021509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Movistar Arena |
E22048
|
entity |
| Predicate | sponsorshipType |
P2590
|
FINISHED |
| Object | naming rights |
—
|
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: naming rights | Statement: [Movistar Arena, sponsorshipType, naming rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorshipType Context triple: [Movistar Arena, sponsorshipType, naming rights]
-
A.
sponsorType
chosen
Indicates the specific role or category of sponsorship that an entity provides in relation to another entity or event.
-
B.
sponsoringOrganizationType
Indicates the kind or category of organization that provides sponsorship or support in the described relationship or activity.
-
C.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
-
D.
sponsorInHouse
Indicates that one entity formally supports, promotes, or funds another entity within the same organization, institution, or internal setting.
-
E.
sponsors
Indicates that one entity provides financial or material support to another, often in exchange for association, promotion, or fulfillment of certain activities or goals.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7dead9c8190a0f8d4ef48e6c809 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b724c7908190a5b92a57fbdbff4e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.