Triple
T25775737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heqet |
E649144
|
entity |
| Predicate | functionInMagic |
P41007
|
FINISHED |
| Object | invoked in spells for safe delivery |
—
|
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: invoked in spells for safe delivery | Statement: [Heqet, functionInMagic, invoked in spells for safe delivery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInMagic Context triple: [Heqet, functionInMagic, invoked in spells for safe delivery]
-
A.
usesMagicFor
chosen
Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
-
B.
functionInRitual
Indicates that an entity serves a specific role or performs a particular function within a ritual.
-
C.
actualFunction
Indicates that something serves as the real, operative function or role performed in practice, as opposed to a nominal or theoretical one.
-
D.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
-
E.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 5:33 a.m.