Triple
T22873949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Wizard’s Guide to Defensive Baking |
E567270
|
entity |
| Predicate | hasMagicSystemType |
P121686
|
FINISHED |
| Object | innate individual magic |
—
|
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: innate individual magic | Statement: [A Wizard’s Guide to Defensive Baking, hasMagicSystemType, innate individual magic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagicSystemType Context triple: [A Wizard’s Guide to Defensive Baking, hasMagicSystemType, innate individual magic]
-
A.
hasMagicSystemElement
Indicates that an entity’s magic system includes or is characterized by a specific elemental component or aspect.
-
B.
hasMagicItem
Indicates that an entity possesses or is associated with a magical item.
-
C.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
D.
featuresMagicSystem
chosen
Indicates that a work includes or is built around a defined system of magic or supernatural powers.
-
E.
hasRitualType
Indicates that an entity is associated with, or classified by, a particular type or category of ritual.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f56d6448190ada4aef08eac2bed |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:39 p.m.