Triple
T28673805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keyhouse |
E725804
|
entity |
| Predicate | originOfMagic |
P40749
|
FINISHED |
| Object | demonic entities from another dimension |
—
|
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: demonic entities from another dimension | Statement: [Keyhouse, originOfMagic, demonic entities from another dimension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfMagic Context triple: [Keyhouse, originOfMagic, demonic entities from another dimension]
-
A.
typeOfMagic
Indicates that one entity is a specific category, school, or kind of magic associated with another entity.
-
B.
knowsAboutMagic
Indicates that one entity possesses knowledge or awareness of magic in relation to another entity or context.
-
C.
viewOfMagic
Indicates a relationship where an entity holds a particular perspective, attitude, or interpretation regarding magic or magical practices.
-
D.
mediumOfMagic
Indicates the medium, channel, or substance through which magic is performed, transmitted, or manifested.
-
E.
originMyth
chosen
Indicates the traditional myth or legendary narrative that explains the beginnings or creation of a people, place, institution, or phenomenon.
- 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_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: April 28, 2026, 5:05 a.m.