Triple
T5164199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DRV PNK Stadium |
E116509
|
entity |
| Predicate | sponsorshipTheme |
P4174
|
FINISHED |
| Object | breast cancer awareness |
—
|
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: breast cancer awareness | Statement: [DRV PNK Stadium, sponsorshipTheme, breast cancer awareness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorshipTheme Context triple: [DRV PNK Stadium, sponsorshipTheme, breast cancer awareness]
-
A.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
-
B.
campaignTheme
chosen
Indicates the central idea or message that characterizes and unifies a particular campaign.
-
C.
sponsorInHouse
Indicates that one entity formally supports, promotes, or funds another entity within the same organization, institution, or internal setting.
-
D.
sponsorshipNameAdopted
Indicates that an entity has adopted or taken on a specific sponsorship name as its official or recognized designation.
-
E.
sponsorEnd
Indicates the point in time or condition at which a sponsorship relationship or sponsorship-related action comes to an end.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd792936d48190825da8826448c1da |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.