Triple
T26346701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolling Thunder |
E662793
|
entity |
| Predicate | associatedWithWrestler |
P198984
|
FINISHED |
| Object | Rob Van Dam |
—
|
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: Rob Van Dam | Statement: [Rolling Thunder, associatedWithWrestler, Rob Van Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWrestler Context triple: [Rolling Thunder, associatedWithWrestler, Rob Van Dam]
-
A.
associatedWrestler
chosen
Indicates that one entity is connected or linked to a particular wrestler, typically through participation, representation, or relevant involvement.
-
B.
wrestledWith
Indicates that one entity engaged in a physical wrestling contest or struggle with another entity.
-
C.
nicknameOfAssociatedWrestler
Indicates that one entity is a nickname that is used to refer to an associated professional wrestler.
-
D.
wrestlerInvolved
Indicates that a wrestler participates in or is directly involved in a particular wrestling-related event or action.
-
E.
managedWrestler
Indicates that one entity served as the manager of another entity in a professional wrestling context.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: April 26, 2026, 10:42 p.m.