Triple
T14103445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connected for Life |
E339440
|
entity |
| Predicate | hasSubgenreCharacteristics |
P45796
|
FINISHED |
| Object | hardcore hip hop |
—
|
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: hardcore hip hop | Statement: [Connected for Life, hasSubgenreCharacteristics, hardcore hip hop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubgenreCharacteristics Context triple: [Connected for Life, hasSubgenreCharacteristics, hardcore hip hop]
-
A.
hasNotableSubgenre
Indicates that one genre is recognized as a particularly significant or prominent subgenre of another genre.
-
B.
hasMusicalStyleCharacteristic
chosen
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
C.
subfamilyCharacteristic
Indicates that a particular characteristic is shared by, or defines, members of a given subfamily.
-
D.
hasMainGenre
Indicates that an entity’s primary or most characteristic genre is the specified genre.
-
E.
hasGenreAsSetting
Indicates that a work’s setting is characterized by, or takes place within, a particular genre.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fbd02888190bf07fd6d8769b61c |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.