Triple
T37160239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Horror |
E920627
|
entity |
| Predicate | isPrimarilySampleBased |
P195114
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Horror, isPrimarilySampleBased, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimarilySampleBased Context triple: [The Horror, isPrimarilySampleBased, true]
-
A.
isRiffDriven
Indicates that something (typically a piece of music) is primarily structured around and propelled by a recurring riff or short musical phrase.
-
B.
isAcoustic
Indicates that something produces sound using natural resonance or mechanical vibration rather than electronic amplification or synthesis.
-
C.
isOneOfTheMostSampledTracksIn
Indicates that a track ranks among those most frequently sampled within a specified context, such as a genre, region, or time period.
-
D.
hasMainInstrumentalElements
Indicates that one entity includes or is characterized by the primary instrumental components or parts of another entity.
-
E.
isInstrumental
Indicates that one entity serves as the means, tool, or instrument by which another entity performs an action or achieves an outcome.
- F. None of above. chosen
Provenance (4 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
| PDg | Predicate description generation | batch_69fda4fe67a08190bdaa84ceabd6de6c |
completed | May 8, 2026, 8:55 a.m. |
Created at: May 3, 2026, 4:15 p.m.