Triple
T34212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | To Anacreon in Heaven |
E680
|
entity |
| Predicate | musicNotationType |
P130
|
FINISHED |
| Object | Western staff notation |
—
|
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: Western staff notation | Statement: [To Anacreon in Heaven, musicNotationType, Western staff notation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicNotationType Context triple: [To Anacreon in Heaven, musicNotationType, Western staff notation]
-
A.
musicTradition
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
-
B.
instrument
Indicates that an action is carried out using a particular tool, means, or implement as its instrument.
-
C.
hasTimeSignature
Indicates that a musical work, passage, or segment is associated with a specific time signature defining its rhythmic meter.
-
D.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
-
E.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
- 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.