Triple
T21446328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | acid-green Quick-Quotes Quill |
E529084
|
entity |
| Predicate | associatedSpellType |
P19914
|
FINISHED |
| Object | enchantments |
—
|
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: enchantments | Statement: [acid-green Quick-Quotes Quill, associatedSpellType, enchantments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSpellType Context triple: [acid-green Quick-Quotes Quill, associatedSpellType, enchantments]
-
A.
typeOfMagic
chosen
Indicates that one entity is a specific category, school, or kind of magic associated with another entity.
-
B.
spells
Indicates that one entity writes or names the letters of a word or sequence in their correct order for another entity or context.
-
C.
relatedSpell
Indicates that there is an association or connection between two spells, such as similarity, dependency, or contextual relevance.
-
D.
includesSpellType
Indicates that one entity (such as a spell list, spellbook, or ability) contains or covers a particular type or category of spell.
-
E.
spellSpecialty
Indicates that an entity’s area of expertise or focus is a particular type or category of spell.
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9cea7bc81909ee3e1cdeda1fe7e |
completed | April 23, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:06 p.m.