Triple
T27879227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bound for Glory |
E705041
|
entity |
| Predicate | formerPromoter |
P194241
|
FINISHED |
| Object | Total Nonstop Action 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: Total Nonstop Action Wrestling | Statement: [Bound for Glory, formerPromoter, Total Nonstop Action Wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerPromoter Context triple: [Bound for Glory, formerPromoter, Total Nonstop Action Wrestling]
-
A.
usesPromoter
Indicates that one entity employs or relies on another entity as a promoter to drive or regulate its activity.
-
B.
laterPromoter
Indicates that one promoter occurs or becomes active at a later time than another promoter in a regulatory or temporal sequence.
-
C.
formerCustom
Indicates that one entity was previously a customer of another entity but is no longer in that role.
-
D.
promotedFrom
Indicates that an entity has advanced to a new position, role, or status from a specified prior one.
-
E.
promotesFrom
Indicates that one entity advances or elevates another entity from a lower position, role, or status to a higher one.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
| PDg | Predicate description generation | batch_69fd68ab21a0819096bfc4a8c14851ad |
completed | May 8, 2026, 4:38 a.m. |
Created at: April 27, 2026, 6:29 p.m.