Triple
T15656639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bell |
E376458
|
entity |
| Predicate | transformsUserInto |
P65473
|
FINISHED |
| Object | cat-like form |
—
|
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: cat-like form | Statement: [Super Bell, transformsUserInto, cat-like form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transformsUserInto Context triple: [Super Bell, transformsUserInto, cat-like form]
-
A.
transformsUnder
Indicates a relationship where one entity changes form, state, or structure when subjected to the influence, conditions, or operation specified by another entity.
-
B.
transformType
Indicates that one entity is converted or changed from its original form into another specified type or form.
-
C.
usesTransformation
Indicates that one entity applies or relies on a specific transformation process, method, or function to operate on or convert another entity.
-
D.
bodyTransformedInto
chosen
Indicates that one entity’s physical form is changed or converted into another specified form or entity.
-
E.
wasTransformedBy
Indicates that an entity has undergone a change of state, form, or condition as the result of an action, process, or agent.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef1f83c8190bbf65eed162cbd55 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.