Triple
T22823045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vic Rattlehead |
E565276
|
entity |
| Predicate | appearanceStyle |
P116832
|
FINISHED |
| Object | horror-inspired |
—
|
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: horror-inspired | Statement: [Vic Rattlehead, appearanceStyle, horror-inspired]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearanceStyle Context triple: [Vic Rattlehead, appearanceStyle, horror-inspired]
-
A.
appearance
Indicates how something looks or seems to an observer, including its visible form, condition, or outward impression.
-
B.
publicAppearance
Indicates that an entity participates in or is present at an event or situation that is open or visible to the general public.
-
C.
characterVisualStyle
chosen
Indicates the visual design or aesthetic style applied to a character, such as their overall look, art style, or graphical presentation.
-
D.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
E.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dd2005081909baef070124eb839 |
completed | April 29, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:34 p.m.