Triple
T8763448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muse Watson |
E208260
|
entity |
| Predicate | genreOfWorkAssociatedWith |
P38924
|
FINISHED |
| Object | slasher film |
—
|
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: slasher film | Statement: [Muse Watson, genreOfWorkAssociatedWith, slasher film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfWorkAssociatedWith Context triple: [Muse Watson, genreOfWorkAssociatedWith, slasher film]
-
A.
genreOfWorkHonored
Indicates the specific genre or type of creative work for which an honor, award, or recognition is given.
-
B.
genreOfWorkDirected
Indicates that a person has directed a work (such as a film, show, or performance) belonging to a specified genre.
-
C.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
D.
genreOfOriginWork
Indicates that a work is classified under a particular genre based on the genre of its original source work.
-
E.
genreAssociatedWith
chosen
Indicates a relationship where a work, item, or entity is linked to or categorized under a particular genre.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dfc85e481909a7ce80c5022e6e9 |
completed | March 31, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.