Triple
T24643252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jessie Douglas Kerruish |
E610032
|
entity |
| Predicate | hasGenreInMostNotableWorks |
P87617
|
FINISHED |
| Object | supernatural fiction |
—
|
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: supernatural fiction | Statement: [Jessie Douglas Kerruish, hasGenreInMostNotableWorks, supernatural fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenreInMostNotableWorks Context triple: [Jessie Douglas Kerruish, hasGenreInMostNotableWorks, supernatural fiction]
-
A.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
B.
seriesGenreOfNotableWork
Indicates that a particular genre characterizes the notable work associated with a series.
-
C.
hasGenreOfWorkItAppearsIn
Indicates that an entity is associated with the genre of the work in which it appears.
-
D.
hasWorkInGenreOfAuthor
Indicates that a work is associated with an author whose typical or primary genre matches the genre of that work.
-
E.
genreOfProducedWorks
chosen
Indicates that one entity is the genre category to which the works produced by another entity belong.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f40db2b5e08190bb55d02a4ceba306 |
completed | May 1, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d2b20881908dcc3b15cbe3e5b0 |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:33 a.m.