Triple
T34265299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Day – Brain Stew / Jaded |
E879149
|
entity |
| Predicate | hasPartStyle |
P78559
|
FINISHED |
| Object | slow and heavy (Brain Stew) |
—
|
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: slow and heavy (Brain Stew) | Statement: [Green Day – Brain Stew / Jaded, hasPartStyle, slow and heavy (Brain Stew)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartStyle Context triple: [Green Day – Brain Stew / Jaded, hasPartStyle, slow and heavy (Brain Stew)]
-
A.
partOfStyle
chosen
Indicates that one style is a component, subset, or constituent element of another, more encompassing style.
-
B.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
C.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
D.
hasSubstyle
Indicates that one style is a more specific or subordinate variant of another style within a hierarchical style structure.
-
E.
hasPowerStyle
Indicates that one entity possesses or exhibits a particular style or manner of using power in relation to another entity or context.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 1, 2026, 1:56 a.m.