Triple
T28667885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unaussprechlichen Kulten |
E725630
|
entity |
| Predicate | authorInFiction |
P106749
|
FINISHED |
| Object | Friedrich von Junzt |
—
|
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: Friedrich von Junzt | Statement: [Unaussprechlichen Kulten, authorInFiction, Friedrich von Junzt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorInFiction Context triple: [Unaussprechlichen Kulten, authorInFiction, Friedrich von Junzt]
-
A.
authorshipInFiction
chosen
Indicates that one entity is the creator or writer of a fictional work in which another entity appears or is represented.
-
B.
producerInFiction
Indicates that an entity serves as a producer (e.g., of a show, film, or other work) within a fictional context or narrative.
-
C.
fictionalUniverseAuthor
Indicates that an author is the creator or primary writer responsible for a given fictional universe.
-
D.
hasFictionalAuthor
Indicates that one entity is the fictional or in-universe author of a work attributed to them.
-
E.
fictionalAuthorVictim
Indicates that one entity is the author of a fictional work in which the other entity appears as a victim.
- 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_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 28, 2026, 5:02 a.m.