Triple
T6730803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idle Hands |
E153627
|
entity |
| Predicate | featuresCreatureOrEntity |
P18264
|
FINISHED |
| Object | demonic hand |
—
|
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: demonic hand | Statement: [Idle Hands, featuresCreatureOrEntity, demonic hand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCreatureOrEntity Context triple: [Idle Hands, featuresCreatureOrEntity, demonic hand]
-
A.
featuresMonster
chosen
Indicates that something includes or prominently presents a monster as part of its content or composition.
-
B.
usesCreature
Indicates that one entity employs, controls, or relies on a creature to perform an action or fulfill a function.
-
C.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
D.
hasCreature
Indicates that one entity possesses, contains, or is associated with a particular creature.
-
E.
enemySpecies
Indicates that two species are in an antagonistic or hostile relationship, typically viewing each other as enemies.
- 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:09 p.m.