Triple
T28668162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R'lyehian |
E725636
|
entity |
| Predicate | firstAppearedInWork |
P115164
|
FINISHED |
| Object | The Call of Cthulhu |
—
|
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: The Call of Cthulhu | Statement: [R'lyehian, firstAppearedInWork, The Call of Cthulhu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAppearedInWork Context triple: [R'lyehian, firstAppearedInWork, The Call of Cthulhu]
-
A.
firstAppearedInWorkBy
Indicates that an entity made its first appearance within a specific work created by a particular author or creator.
-
B.
firstPerformanceOfWorkAppearedIn
Indicates that a given performance is the earliest known or documented performance in which a particular work was presented or appeared.
-
C.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
D.
firstPublicationIn
Indicates the initial venue, medium, or context in which a work was first published.
-
E.
firstAppearanceBook
chosen
Indicates the book in which an entity (such as a character or concept) is first introduced or appears.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: April 28, 2026, 5:02 a.m.