Triple
T26346724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolling Thunder |
E662793
|
entity |
| Predicate | signatureMoveOf |
P62555
|
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, signatureMoveOf, Rob Van Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureMoveOf Context triple: [Rolling Thunder, signatureMoveOf, Rob Van Dam]
-
A.
usesSignatureMove
Indicates that an entity performs or employs a distinctive, characteristic move or technique associated specifically with it.
-
B.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
C.
signatureManeuver
chosen
Indicates a distinctive or characteristic action or move that an entity is especially known for performing.
-
D.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
E.
signFeature
Indicates that an entity bears or displays a particular sign, symbol, or distinguishing feature.
- 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_69f60fa7f0588190988ce7483ab7523d |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 10:42 p.m.