Triple
T28521017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur |
E721764
|
entity |
| Predicate | bodyHorrorElement |
P64901
|
FINISHED |
| Object | eyes appearing on his hands |
—
|
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: eyes appearing on his hands | Statement: [Arthur, bodyHorrorElement, eyes appearing on his hands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyHorrorElement Context triple: [Arthur, bodyHorrorElement, eyes appearing on his hands]
-
A.
hasHorrorElements
chosen
Indicates that something contains features, themes, or stylistic aspects characteristic of the horror genre.
-
B.
deathSceneFeature
Indicates that a particular feature, element, or characteristic is present in the scene depicting a character’s death.
-
C.
deathAttracting
Indicates a relationship where one entity’s death draws, lures, or otherwise causes another entity to come closer or be attracted.
-
D.
oreBody
Indicates that one entity is an ore body, i.e., a naturally occurring concentration of minerals in the context of the other entity.
-
E.
bodyPartsGiveRiseTo
Indicates that certain body parts develop into, generate, or are the source of other anatomical structures or tissues.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fa24a6481908c8b6651cbaf0664 |
completed | May 2, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:20 a.m.