Triple
T26944721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Snow White universe |
E678605
|
entity |
| Predicate | hasMagicalElement |
P97183
|
FINISHED |
| Object | Magic Mirror |
—
|
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: Magic Mirror | Statement: [Disney Snow White universe, hasMagicalElement, Magic Mirror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagicalElement Context triple: [Disney Snow White universe, hasMagicalElement, Magic Mirror]
-
A.
hasMagicSystemElement
Indicates that an entity’s magic system includes or is characterized by a specific elemental component or aspect.
-
B.
hasRoleInElementals
Indicates that an entity holds a specific role or function within a group, system, or context referred to as "Elementals".
-
C.
hasMagicItem
chosen
Indicates that an entity possesses or is associated with a magical item.
-
D.
hasMagicCompanion
Indicates that an entity is accompanied by or associated with another entity that serves as its magical companion.
-
E.
hasLimitedMagic
Indicates that an entity possesses magical abilities that are restricted in scope, power, frequency, or conditions of use.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 27, 2026, 6:20 a.m.