Triple
T32419359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Chop 2 |
E828408
|
entity |
| Predicate | featuresHardHittingProduction |
P152748
|
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: [King Chop 2, featuresHardHittingProduction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresHardHittingProduction Context triple: [King Chop 2, featuresHardHittingProduction, true]
-
A.
featuresHeavyProduction
Indicates that something involves intensive, large-scale, or complex production work, often requiring substantial resources or effort.
-
B.
featuresAggressiveProductionStyle
chosen
Indicates that the subject’s production is characterized by intense, forceful, or hard-hitting stylistic choices.
-
C.
featuresDarkProduction
Indicates that something includes or is characterized by a dark or moody style of production.
-
D.
hasBassHeavyProduction
Indicates that the music’s production emphasizes low-frequency sounds, giving it a strong, prominent bass presence.
-
E.
productionFeature
Indicates that something is a characteristic, element, or attribute involved in the process or method of producing something.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00dc330b148190aaae2ac6a5327960 |
completed | May 10, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_6a00d9d2904881909dafbfe7b9e5ad81 |
completed | May 10, 2026, 7:17 p.m. |
Created at: May 1, 2026, 12:54 a.m.