Triple
T23723047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enochian magic |
E586195
|
entity |
| Predicate | receivedThrough |
P139521
|
FINISHED |
| Object | John Dee's scrying sessions |
—
|
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: John Dee's scrying sessions | Statement: [Enochian magic, receivedThrough, John Dee's scrying sessions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedThrough Context triple: [Enochian magic, receivedThrough, John Dee's scrying sessions]
-
A.
receivedIn
chosen
Indicates that something was obtained, accepted, or taken possession of within a particular context, location, or time frame.
-
B.
receivedTransmissionOf
Indicates that one entity has obtained or been sent a transmission (such as a message, signal, or data) originating from another entity.
-
C.
receivedFor
Indicates that something was obtained, accepted, or taken into possession on behalf of or for the benefit of a specified entity.
-
D.
receivedSign
Indicates that one entity has obtained or been given a sign (such as a signal, symbol, or indication) from another entity.
-
E.
receivedSupportFrom
Indicates that one entity obtained help, resources, or backing from another entity.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b912a7548190afcfa03dd9adc47e |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:05 p.m.