Triple
T25001503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bash at the Beach |
E625729
|
entity |
| Predicate | successorEventNameUsedBy |
P72548
|
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: [Bash at the Beach, successorEventNameUsedBy, Total Nonstop Action Wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorEventNameUsedBy Context triple: [Bash at the Beach, successorEventNameUsedBy, Total Nonstop Action Wrestling]
-
A.
successorUsedIn
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of another entity.
-
B.
succeededByEvent
chosen
Indicates that one event directly follows and replaces another in a temporal or sequential order.
-
C.
eventualSuccessor
Indicates that one entity will become the successor of another at some later point in time, rather than immediately.
-
D.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
-
E.
namedAfterSuccessor
Indicates that an entity is named after another entity that succeeds or follows it in time, position, or sequence.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 18, 2026, 6:04 a.m.