Triple
T29037988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania 36 |
E737916
|
entity |
| Predicate | brandInvolvement |
P83721
|
FINISHED |
| Object | Raw |
—
|
NE NERFINISHED |
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: Raw | Statement: [WrestleMania 36, brandInvolvement, Raw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandInvolvement Context triple: [WrestleMania 36, brandInvolvement, Raw]
-
A.
brandInvolved
chosen
Indicates that a particular brand participates in, is associated with, or plays a role in the specified event, activity, or context.
-
B.
brandIntegration
Indicates the incorporation of a brand’s identity, products, or messaging into another medium, experience, or content in a coordinated and often seamless way.
-
C.
brandVisibility
Indicates how prominently and frequently a brand is noticed or recognized by its target audience across relevant channels.
-
D.
brandEndorsement
Indicates that one entity publicly supports, recommends, or promotes another entity’s brand, product, or service.
-
E.
brandingCollaboration
Indicates a cooperative relationship where entities work together on branding-related activities, such as co-developing or jointly promoting brand identity, image, or marketing materials.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 10 a.m.