Triple
T25508117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acrasia |
E639298
|
entity |
| Predicate | methodOfEnchantment |
P159766
|
FINISHED |
| Object | sensual delights |
—
|
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: sensual delights | Statement: [Acrasia, methodOfEnchantment, sensual delights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfEnchantment Context triple: [Acrasia, methodOfEnchantment, sensual delights]
-
A.
enchantedBy
Indicates that one entity has cast or holds a magical enchantment over another entity.
-
B.
enchantment
Indicates that one entity has placed a magical or supernatural influence on another, altering its state, behavior, or properties.
-
C.
canBeEnchantedWith
Indicates that an entity is capable of receiving or being affected by a specified enchantment.
-
D.
enchantedAs
Indicates that one entity has been placed under a magical spell or charm by another entity or force.
-
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. chosen
Provenance (4 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f80749f88190a5c2a70e7370003b |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 21, 2026, 2:47 p.m.