Triple
T24711072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Emperor’s Soul |
E612027
|
entity |
| Predicate | containsMagicSystemType |
P49967
|
FINISHED |
| Object | symbol-based 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: symbol-based magic | Statement: [The Emperor’s Soul, containsMagicSystemType, symbol-based magic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMagicSystemType Context triple: [The Emperor’s Soul, containsMagicSystemType, symbol-based magic]
-
A.
hasMagicSystemElement
Indicates that an entity’s magic system includes or is characterized by a specific elemental component or aspect.
-
B.
associatedWithMagicType
chosen
Indicates a relationship where something is linked or connected to a particular type or category of magic.
-
C.
hasMagicItem
Indicates that an entity possesses or is associated with a magical item.
-
D.
featuresMagicSystem
Indicates that a work includes or is built around a defined system of magic or supernatural powers.
-
E.
usesMagicFor
Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 18, 2026, 3:24 a.m.