Triple
T38383419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hårga |
E893814
|
entity |
| Predicate | toneContrast |
P177074
|
FINISHED |
| Object | bright daylight horror setting |
—
|
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: bright daylight horror setting | Statement: [Hårga, toneContrast, bright daylight horror setting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toneContrast Context triple: [Hårga, toneContrast, bright daylight horror setting]
-
A.
toneContrastWith
chosen
Indicates that one entity’s tone differs noticeably from, and is contrasted against, the tone of another entity.
-
B.
textureContrast
Indicates a relationship where two surfaces or regions differ noticeably in their tactile or visual texture qualities.
-
C.
tempoContrast
Indicates a relationship where two musical passages or sections differ in tempo, highlighting a contrast in their speed or pacing.
-
D.
contrastEffect
Indicates that one entity’s characteristics are perceived or evaluated differently because they are compared or juxtaposed with another entity.
-
E.
achievesContrast
Indicates that one entity creates or enhances a visual or conceptual difference relative to another entity.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.