Triple
T16440027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You're Crazy |
E399273
|
entity |
| Predicate | hasRockSubgenre |
P122796
|
FINISHED |
| Object | sleaze rock |
—
|
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: sleaze rock | Statement: [You're Crazy, hasRockSubgenre, sleaze rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockSubgenre Context triple: [You're Crazy, hasRockSubgenre, sleaze rock]
-
A.
hasRockRecord
Indicates that an entity possesses or is associated with a documented record related to rock music or rock materials.
-
B.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
C.
hasNotableSubgenre
Indicates that one genre is recognized as a particularly significant or prominent subgenre of another genre.
-
D.
hasMainGenre
Indicates that an entity’s primary or most characteristic genre is the specified genre.
-
E.
hasRockArchName
Indicates that a rock arch is associated with a specific name or designation.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba720a48190b0b412225e993e52 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.