Triple
T31823788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cedric the Sorcerer |
E812336
|
entity |
| Predicate | typicalMagicStyle |
P152566
|
FINISHED |
| Object | incantation-based spells |
—
|
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: incantation-based spells | Statement: [Cedric the Sorcerer, typicalMagicStyle, incantation-based spells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMagicStyle Context triple: [Cedric the Sorcerer, typicalMagicStyle, incantation-based spells]
-
A.
magicStyle
chosen
Indicates the manner or type of magic used or expressed in a magical action or relationship.
-
B.
typeOfMagic
Indicates that one entity is a specific category, school, or kind of magic associated with another entity.
-
C.
magical
Indicates that one entity possesses, uses, or is characterized by supernatural or mystical powers in relation to another entity or context.
-
D.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
-
E.
involvesMagic
Indicates that the related action, event, or relationship includes the use or presence of magical powers, forces, or phenomena.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:46 p.m.