Triple
T35806391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock Bottom |
E1035110
|
entity |
| Predicate | usedAsSignatureMove |
P108696
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rock Bottom, usedAsSignatureMove, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsSignatureMove Context triple: [Rock Bottom, usedAsSignatureMove, yes]
-
A.
usesSignatureMove
chosen
Indicates that an entity performs or employs a distinctive, characteristic move or technique associated specifically with it.
-
B.
introducedAsSignatureMoveOf
Indicates that one entity was presented or established as the signature move or defining technique of another entity (such as a character, performer, or brand).
-
C.
usedInSignature
Indicates that something (such as a method, type, or value) appears as part of the formal signature or interface definition of another construct.
-
D.
usesSignature
Indicates that one entity employs or relies on the specific signature (e.g., cryptographic, digital, or formal) associated with another entity for validation, identification, or authorization purposes.
-
E.
usedInSignatureOf
Indicates that something (such as a type, parameter, or construct) appears as part of the formal signature of a function, method, or similar callable entity.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: May 3, 2026, 4:06 p.m.