Triple
T35011490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwemer |
E1009947
|
entity |
| Predicate | magicDiscipline |
P19914
|
FINISHED |
| Object | tonal manipulation |
—
|
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: tonal manipulation | Statement: [Dwemer, magicDiscipline, tonal manipulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magicDiscipline Context triple: [Dwemer, magicDiscipline, tonal manipulation]
-
A.
typeOfMagic
chosen
Indicates that one entity is a specific category, school, or kind of magic associated with another entity.
-
B.
psionicDiscipline
Indicates that an entity practices, specializes in, or is associated with a particular psionic discipline or mental power tradition.
-
C.
spellSpecialty
Indicates that an entity’s area of expertise or focus is a particular type or category of spell.
-
D.
spells
Indicates that one entity writes or names the letters of a word or sequence in their correct order for another entity or context.
-
E.
magicAffinity
Indicates a relationship where an entity possesses a natural connection to, talent for, or compatibility with magical forces or energies.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.