Triple
T36475364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gel |
E898645
|
entity |
| Predicate | hasEnergeticGuitarRiffs |
P112603
|
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: [Gel, hasEnergeticGuitarRiffs, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergeticGuitarRiffs Context triple: [Gel, hasEnergeticGuitarRiffs, true]
-
A.
hasGuitarRiffs
Indicates that one entity features or contains guitar riffs provided or performed by another entity.
-
B.
hasAggressiveRiffs
chosen
Indicates that something features intense, forceful, or hard-edged musical riffs.
-
C.
hasNotableGuitarRiffBy
Indicates that something (typically a song or musical piece) is characterized by a notable guitar riff performed or created by a specified guitarist.
-
D.
hasRiffs
Indicates that one entity features or contains musical riffs associated with another entity.
-
E.
hasRhythmGuitar
Indicates that an entity includes or features a rhythm guitar as part of its musical instrumentation or arrangement.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:10 p.m.