Triple
T35842548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tombstone Piledriver |
E1036122
|
entity |
| Predicate | relatedMove |
P206072
|
FINISHED |
| Object | piledriver |
—
|
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: piledriver | Statement: [Tombstone Piledriver, relatedMove, piledriver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedMove Context triple: [Tombstone Piledriver, relatedMove, piledriver]
-
A.
relatedTransition
Indicates a connection between two transitions, showing that one transition is associated with, derived from, or contextually linked to the other.
-
B.
commonMove
Indicates that two or more entities share the same movement or relocation event, occurring together or in an identical manner.
-
C.
relocatedBetween
Indicates that an entity changed location from one place to another during a specified time interval or between two reference points.
-
D.
movedBy
Indicates that an entity changes position or location as a result of another entity’s action or influence.
-
E.
clubMove
Indicates a change in a person's club affiliation, capturing the action of moving from one club to another.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.