Triple
T7416093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silverdome |
E171133
|
entity |
| Predicate | hostedPromotion |
P2777
|
FINISHED |
| Object | World Wrestling Federation events |
—
|
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: World Wrestling Federation events | Statement: [Silverdome, hostedPromotion, World Wrestling Federation events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedPromotion Context triple: [Silverdome, hostedPromotion, World Wrestling Federation events]
-
A.
hosted
chosen
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
-
B.
promotionFrom
Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
-
C.
promotionType
Indicates the specific kind or category of promotion associated with an entity or event.
-
D.
announcedPromotion
Indicates that an entity has publicly communicated the start or existence of a promotion or special offer to others.
-
E.
promotionalCampaign
Indicates a relationship where one entity organizes or runs a coordinated set of marketing activities aimed at promoting another entity, product, or service.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c643248190a387abba2f482b25 |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.