Triple
T26917958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lena |
E677563
|
entity |
| Predicate | createdByMagicOf |
P46127
|
FINISHED |
| Object | Magica De Spell |
—
|
NE NERFINISHED |
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: Magica De Spell | Statement: [Lena, createdByMagicOf, Magica De Spell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdByMagicOf Context triple: [Lena, createdByMagicOf, Magica De Spell]
-
A.
enchantedBy
chosen
Indicates that one entity has cast or holds a magical enchantment over another entity.
-
B.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
-
C.
isFictionallyCreatedBy
Indicates that an entity is a fictional creation authored, invented, or brought into existence within a narrative by another entity.
-
D.
usesMagicFor
Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
-
E.
enchantedTo
Indicates that one entity has been magically imbued or altered so that it possesses a special effect, property, or behavior caused by another entity.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 27, 2026, 6:05 a.m.