Triple
T181267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Manchester Stadium |
E3880
|
entity |
| Predicate | sponsorshipDealStart |
P6314
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [City of Manchester Stadium, sponsorshipDealStart, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorshipDealStart Context triple: [City of Manchester Stadium, sponsorshipDealStart, 2011]
-
A.
coSponsor
Indicates that an entity jointly supports, endorses, or backs an initiative, proposal, or activity together with one or more others.
-
B.
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.
-
C.
sportsSponsored
Indicates that one entity provides financial or material sponsorship to support another entity’s sports-related activities or events.
-
D.
sponsorType
Indicates the specific role or category of sponsorship that an entity provides in relation to another entity or event.
-
E.
contractStartSeason
Indicates the season during which a contract between entities begins or becomes effective.
- F. None of above. chosen
Provenance (4 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25923507c8190bd7f6eda404b0da0 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566ccc288190add5624ede96d82b |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2575e7c7c819095167d8a862c255a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.