Triple
T22392207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Number of the Beast |
E553536
|
entity |
| Predicate | containsMusicalFeature |
P44121
|
FINISHED |
| Object | twin-guitar harmonies |
—
|
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: twin-guitar harmonies | Statement: [The Number of the Beast, containsMusicalFeature, twin-guitar harmonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMusicalFeature Context triple: [The Number of the Beast, containsMusicalFeature, twin-guitar harmonies]
-
A.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
B.
hasMusicCharacteristic
chosen
Indicates that an entity possesses a specific musical feature, quality, or attribute.
-
C.
hasMusicalSettingsBy
Indicates that a work has been set to music or musically arranged by a specified creator or composer.
-
D.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
E.
hasAudioFeature
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1585c16188190872e75caeb86c328 |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.