Triple
T16099007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock-a-Beatin' Boogie |
E390562
|
entity |
| Predicate | inTheStyleOf |
P121907
|
FINISHED |
| Object | Bill Haley & His Comets sound |
—
|
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: Bill Haley & His Comets sound | Statement: [Rock-a-Beatin' Boogie, inTheStyleOf, Bill Haley & His Comets sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inTheStyleOf Context triple: [Rock-a-Beatin' Boogie, inTheStyleOf, Bill Haley & His Comets sound]
-
A.
personHasNotableStyle
Indicates that a person is recognized for having a distinctive or noteworthy style.
-
B.
fashionStyle
Indicates the characteristic way in which an entity dresses or presents themselves in terms of clothing and appearance.
-
C.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
-
D.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
E.
exploresStyle
Indicates that one entity investigates, examines, or experiments with the style or stylistic characteristics of another entity.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6672848190922b5ebb90e18947 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:59 a.m.