Triple
T8316329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Necronomicon |
E194714
|
entity |
| Predicate | fictionalAuthorDescription |
P68311
|
FINISHED |
| Object | mad Arab poet |
—
|
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: mad Arab poet | Statement: [Necronomicon, fictionalAuthorDescription, mad Arab poet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalAuthorDescription Context triple: [Necronomicon, fictionalAuthorDescription, mad Arab poet]
-
A.
hasFictionalAuthor
chosen
Indicates that one entity is the fictional or in-universe author of a work attributed to them.
-
B.
fictionalNarrator
Indicates that one entity serves as the narrator or storytelling voice within a fictional work that features the other entity.
-
C.
describedByAuthorAs
Indicates that one entity is characterized, labeled, or portrayed in a particular way by an author.
-
D.
producerInFiction
Indicates that an entity serves as a producer (e.g., of a show, film, or other work) within a fictional context or narrative.
-
E.
authorOfDescription
Indicates that an entity is the creator or writer of a particular description or explanatory text about something.
- 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_69cb7f557a7881908adcf353f7297848 |
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.