Triple
T26630100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plumette |
E668466
|
entity |
| Predicate | enchantedInto |
P161071
|
FINISHED |
| Object | feather duster |
—
|
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: feather duster | Statement: [Plumette, enchantedInto, feather duster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enchantedInto Context triple: [Plumette, enchantedInto, feather duster]
-
A.
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.
-
B.
enchantedBy
Indicates that one entity has cast or holds a magical enchantment over another entity.
-
C.
enchantedAs
Indicates that one entity has been placed under a magical spell or charm by another entity or force.
-
D.
enchantable
Indicates that an entity is capable of being affected by or imbued with magical enchantments.
-
E.
enchantedToAppearTo
Indicates that one entity has been magically altered or configured so that it visually manifests or becomes visible to another specified entity or group.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f615ed5e408190b03300231f23bdfc |
completed | May 2, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 2:24 a.m.