Triple
T28825152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Lumley |
E727879
|
entity |
| Predicate | literaryUniverseContributedTo |
P174380
|
FINISHED |
| Object | Cthulhu Mythos |
—
|
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: Cthulhu Mythos | Statement: [Brian Lumley, literaryUniverseContributedTo, Cthulhu Mythos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryUniverseContributedTo Context triple: [Brian Lumley, literaryUniverseContributedTo, Cthulhu Mythos]
-
A.
workAuthoredInUniverse
Indicates that a creative work is set within, or narratively belongs to, a particular fictional or conceptual universe.
-
B.
literaryUniverse
Indicates that two or more works of literature exist within the same fictional universe or continuity, sharing settings, characters, or canonical events.
-
C.
hasAssociatedWorkOfFiction
Indicates that an entity is linked to a related work of fiction, such as a novel, film, or story that is associated with it.
-
D.
workWrittenFor
Indicates that a creative work was specifically composed, produced, or created for a particular person, group, event, purpose, or medium.
-
E.
genreOfWorkContributedTo
Indicates that an entity contributed to a work belonging to a specified genre.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 28, 2026, 6:35 a.m.