Triple
T28668244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdul Alhazred |
E725637
|
entity |
| Predicate | fictionalActivity |
P185944
|
FINISHED |
| Object | communing with eldritch entities |
—
|
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: communing with eldritch entities | Statement: [Abdul Alhazred, fictionalActivity, communing with eldritch entities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalActivity Context triple: [Abdul Alhazred, fictionalActivity, communing with eldritch entities]
-
A.
fictionalContent
Indicates that one entity is content whose subject matter, events, or characters are imaginary or invented rather than factual.
-
B.
literaryActivity
Indicates involvement in creating, studying, or engaging with written works such as literature, poetry, or scholarly texts.
-
C.
fictionalType
Indicates that one entity is a fictional or imaginary type or category of the other entity.
-
D.
fictionalFocus
Indicates that the primary emphasis or attention within a context is placed on fictional content, elements, or aspects.
-
E.
fictionalSon
Indicates that one entity is portrayed as the son of another entity within a fictional or narrative context.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: April 28, 2026, 5:02 a.m.