Triple
T9138390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMLL Anniversary Show |
E219261
|
entity |
| Predicate | featuresPromotionRoster |
P87332
|
FINISHED |
| Object | CMLL wrestlers |
—
|
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: CMLL wrestlers | Statement: [CMLL Anniversary Show, featuresPromotionRoster, CMLL wrestlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPromotionRoster Context triple: [CMLL Anniversary Show, featuresPromotionRoster, CMLL wrestlers]
-
A.
featuresFranchise
Indicates that one entity includes or presents a particular franchise as part of its content, offering, or composition.
-
B.
promotedIn
Indicates that an entity was advanced to a higher rank, position, or status during a specified time or event.
-
C.
featuresHero
Indicates that something (such as a work, product, or story) prominently includes or centers around a particular hero as a main character or focus.
-
D.
promotionType
Indicates the specific kind or category of promotion associated with an entity or event.
-
E.
promotionalFor
Indicates that one entity serves to advertise, market, or otherwise promote another entity, such as a product, service, event, or brand.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8efe3b88190a55a15827e6817a4 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:19 p.m.