Triple
T34221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | To Anacreon in Heaven |
E680
|
entity |
| Predicate | musicStyle |
P526
|
FINISHED |
| Object | late 18th-century English song style |
—
|
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: late 18th-century English song style | Statement: [To Anacreon in Heaven, musicStyle, late 18th-century English song style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicStyle Context triple: [To Anacreon in Heaven, musicStyle, late 18th-century English song style]
-
A.
musicTradition
chosen
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
-
B.
genre
Indicates the artistic or thematic category to which a work (such as a book, film, or song) belongs.
-
C.
artisticStyle
Indicates the artistic movement, style, or aesthetic approach that characterizes how something is created or visually expressed.
-
D.
worshipStyle
Indicates the manner or form in which worship or religious devotion is practiced or expressed.
-
E.
melodyOrigin
Indicates the source or provenance from which a particular melody is derived or originally created.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490019948190a89bb0910c60d462 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a24872e4e481908567850168d65015 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.