Triple
T29470251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intentions of Murder |
E747488
|
entity |
| Predicate | directorStyleContext |
P70207
|
FINISHED |
| Object | Japanese New Wave |
—
|
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: Japanese New Wave | Statement: [Intentions of Murder, directorStyleContext, Japanese New Wave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorStyleContext Context triple: [Intentions of Murder, directorStyleContext, Japanese New Wave]
-
A.
directedInStyle
chosen
Indicates that a work was directed in a particular stylistic manner or according to a specific directing style.
-
B.
directorialStyle
Indicates the characteristic manner or approach a director consistently uses in creating and shaping their works.
-
C.
performanceStyle
Indicates the manner or style in which an action, work, or performance is carried out or presented.
-
D.
stylisticElement
Indicates a relationship where one entity functions as a stylistic feature, device, or characteristic that shapes the expressive or aesthetic quality of another entity.
-
E.
dedicatedToStyleOf
Indicates that something is devoted or specifically tailored to a particular style or manner of expression.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 28, 2026, 3:56 p.m.