Triple
T37662411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ender Pearl |
E937744
|
entity |
| Predicate | canBeEnchantedVia |
P100799
|
FINISHED |
| Object | Enchanted books affecting projectiles (e.g. via crossbow)? |
—
|
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: Enchanted books affecting projectiles (e.g. via crossbow)? | Statement: [Ender Pearl, canBeEnchantedVia, Enchanted books affecting projectiles (e.g. via crossbow)?]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeEnchantedVia Context triple: [Ender Pearl, canBeEnchantedVia, Enchanted books affecting projectiles (e.g. via crossbow)?]
-
A.
canBeEnchantedWith
chosen
Indicates that an entity is capable of receiving or being affected by a specified enchantment.
-
B.
cannotBeEnchantedWith
Indicates that an entity is not eligible or allowed to receive a specified enchantment.
-
C.
cannotBeEnchanted
Indicates that the subject is not capable of being affected or altered by enchantments or magical enhancements.
-
D.
isDisenchantable
Indicates that an item or object can be broken down or nullified using a disenchanting process.
-
E.
enchantmentType
Indicates the specific kind or category of magical enchantment associated with an entity or effect.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:18 p.m.