Triple
T27739940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Tag Team Championship |
E701824
|
entity |
| Predicate | introducedInPromotion |
P180496
|
FINISHED |
| Object | TNA |
—
|
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: TNA | Statement: [World Tag Team Championship, introducedInPromotion, TNA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInPromotion Context triple: [World Tag Team Championship, introducedInPromotion, TNA]
-
A.
usesPromotion
Indicates that an entity applies or takes advantage of a specific promotion, discount, or special offer.
-
B.
announcedPromotion
Indicates that an entity has publicly communicated the start or existence of a promotion or special offer to others.
-
C.
associatedWithPromotion
Indicates a relationship in which an entity is connected to, involved in, or affected by a specific promotion or promotional activity.
-
D.
usesPromotionFrom
Indicates that one entity applies or benefits from a promotion, discount, or marketing offer provided or originated by another entity.
-
E.
introducedInAdvertisingCampaign
Indicates that an entity was first presented or made known to the public as part of a specific advertising campaign.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 27, 2026, 4:09 p.m.