Triple
T9226011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMLL Homenaje a Dos Leyendas |
E221683
|
entity |
| Predicate | replacesEvent |
P37946
|
FINISHED |
| Object | CMLL Anniversary Show for that date slot |
—
|
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 Anniversary Show for that date slot | Statement: [CMLL Homenaje a Dos Leyendas, replacesEvent, CMLL Anniversary Show for that date slot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesEvent Context triple: [CMLL Homenaje a Dos Leyendas, replacesEvent, CMLL Anniversary Show for that date slot]
-
A.
replacedAfterEvent
Indicates that one entity takes the place of another entity following a specified event or occurrence.
-
B.
alternativeEvent
chosen
Indicates that one event serves as an alternative or substitute option to another event within the same context.
-
C.
replacedCalendar
Indicates that one calendar has been substituted or superseded by another calendar.
-
D.
renamedAfterEvent
Indicates that an entity has changed its name as a consequence of, or in commemoration of, a specific event.
-
E.
repealedAfterEvent
Indicates that a law or regulation was repealed as a consequence of, or following, a specific event.
- 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_69ca83ec8db08190a9110df8232885d2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda9dbd1481909f35a4bee8e0b450 |
completed | April 1, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:28 p.m.