Triple
T24204602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tazz |
E600071
|
entity |
| Predicate | roleInPromotion |
P13067
|
FINISHED |
| Object | ECW main event wrestler |
—
|
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: ECW main event wrestler | Statement: [Tazz, roleInPromotion, ECW main event wrestler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPromotion Context triple: [Tazz, roleInPromotion, ECW main event wrestler]
-
A.
promotionalRole
chosen
Indicates that an entity serves in a capacity focused on promoting, advertising, or publicizing another entity, product, or activity.
-
B.
isPromotedAs
Indicates that one entity is advertised, marketed, or presented to others in a particular way or role by another entity.
-
C.
hasBeenPromotedBy
Indicates that one entity has received a promotion as a result of the decision or action taken by another entity.
-
D.
arePromotedBy
Indicates that one entity advances in rank, position, or status as a result of an action or decision made by another entity.
-
E.
bearerPromotion
Indicates a relationship where a bearer (such as a card, token, or credential holder) is granted or associated with a specific promotion or promotional offer.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca52cb881908c99913ea93bc88e |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:37 p.m.