Triple
T34202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | To Anacreon in Heaven |
E680
|
entity |
| Predicate | accompaniment |
P162
|
FINISHED |
| Object | keyboard accompaniment |
—
|
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: keyboard accompaniment | Statement: [To Anacreon in Heaven, accompaniment, keyboard accompaniment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accompaniment Context triple: [To Anacreon in Heaven, accompaniment, keyboard accompaniment]
-
A.
instrument
Indicates that an action is carried out using a particular tool, means, or implement as its instrument.
-
B.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
-
C.
complements
chosen
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
D.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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.