Triple
T30756352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tritonian Ring |
E783093
|
entity |
| Predicate | containsMagicSystem |
P121686
|
FINISHED |
| Object | ritual-based sorcery |
—
|
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: ritual-based sorcery | Statement: [The Tritonian Ring, containsMagicSystem, ritual-based sorcery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMagicSystem Context triple: [The Tritonian Ring, containsMagicSystem, ritual-based sorcery]
-
A.
hasMagicSystemElement
Indicates that an entity’s magic system includes or is characterized by a specific elemental component or aspect.
-
B.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
-
C.
usesMagicFor
Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
-
D.
featuresMagicSystem
chosen
Indicates that a work includes or is built around a defined system of magic or supernatural powers.
-
E.
hasAccessToMagic
Indicates that one entity is able to use, interact with, or benefit from magical powers, resources, or abilities associated with another entity or source.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: April 29, 2026, 8:39 p.m.