Triple
T35809048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RK-Bro |
E1035178
|
entity |
| Predicate | signatureMoveTheme |
P184199
|
FINISHED |
| Object | RKO-based offense |
—
|
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: RKO-based offense | Statement: [RK-Bro, signatureMoveTheme, RKO-based offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureMoveTheme Context triple: [RK-Bro, signatureMoveTheme, RKO-based offense]
-
A.
signatureTheme
Indicates that something serves as a distinctive, defining theme strongly associated with a particular entity or context.
-
B.
thematicMove
Indicates a movement or change that develops, transforms, or shifts an existing theme within a work or sequence.
-
C.
transformationTheme
Indicates a thematic relationship in which one entity centers on or explores the process, experience, or idea of transformation in another.
-
D.
signFeature
Indicates that an entity bears or displays a particular sign, symbol, or distinguishing feature.
-
E.
shapeTheme
Indicates a relationship where one entity’s form, outline, or geometric characteristics serve as a central motif or organizing principle for another entity.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7ac2210e481909279dade5328825c |
completed | May 3, 2026, 8:12 p.m. |
Created at: May 3, 2026, 4:06 p.m.