Triple
T8315959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Call of Cthulhu |
E194706
|
entity |
| Predicate | hasMottoOrPhrase |
P23882
|
FINISHED |
| Object | Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn |
—
|
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: Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn | Statement: [The Call of Cthulhu, hasMottoOrPhrase, Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoOrPhrase Context triple: [The Call of Cthulhu, hasMottoOrPhrase, Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn]
-
A.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
B.
hasMottoInText
chosen
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
C.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
D.
hasMottoContext
Indicates that an entity’s motto is associated with or applies within a specific contextual setting or scope.
-
E.
hasMottoOrigin
Indicates that a motto originates from, or is derived from, a particular source, place, or context.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f540b2081908ccb1b2ed040c74e |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.