Triple
T21188820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hidimbi |
E522157
|
entity |
| Predicate | transformationAbility |
P120301
|
FINISHED |
| Object | shape-shifting |
—
|
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: shape-shifting | Statement: [Hidimbi, transformationAbility, shape-shifting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transformationAbility Context triple: [Hidimbi, transformationAbility, shape-shifting]
-
A.
usesTransformation
Indicates that one entity applies or relies on a specific transformation process, method, or function to operate on or convert another entity.
-
B.
featuresTransformationOf
Indicates that something includes or presents a transformation or change applied to another entity.
-
C.
canTransform
chosen
Indicates that one entity is capable of being changed or converted into another entity or state.
-
D.
transformationDevice
Indicates that one entity functions as a device or mechanism used to transform, convert, or change another entity or its state.
-
E.
transformationProperty
Indicates that one entity has a specific behavior, constraint, or characteristic related to how it changes, converts, or is transformed into another form or state.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733350e588190a31467758a8afa5c |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.