Triple
T24204752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Booker T |
E600074
|
entity |
| Predicate | promotionFounded |
P155197
|
FINISHED |
| Object | Reality of Wrestling |
—
|
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: Reality of Wrestling | Statement: [Booker T, promotionFounded, Reality of Wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionFounded Context triple: [Booker T, promotionFounded, Reality of Wrestling]
-
A.
promotionBy
Indicates that one entity advances, elevates, or publicizes another entity, typically by increasing its status, visibility, or level.
-
B.
promotionFrom
Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
-
C.
promotionInvolved
Indicates that an entity participated in or was associated with a promotional activity, campaign, or marketing effort.
-
D.
sponsorFrom
Indicates that one entity provides sponsorship or financial backing originating from a specified source entity.
-
E.
sponsorTo
Indicates that one entity provides support, funding, or endorsement to another entity, typically to enable or promote the latter’s activities or initiatives.
- 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_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. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:37 p.m.