Triple
T38443315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prayer in Open D |
E906564
|
entity |
| Predicate | hasMusicalTuning |
P30142
|
FINISHED |
| Object | open D tuning |
—
|
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: open D tuning | Statement: [Prayer in Open D, hasMusicalTuning, open D tuning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalTuning Context triple: [Prayer in Open D, hasMusicalTuning, open D tuning]
-
A.
hasTuningDivision
Indicates that one entity specifies or uses a particular system or scheme for dividing a range (such as a musical interval or scale) into tuning units.
-
B.
tuningOfInstrument
chosen
Indicates the specific tuning configuration or pitch arrangement applied to a musical instrument.
-
C.
tunedOrUntuned
Indicates whether something is in a properly adjusted or calibrated state (tuned) or not (untuned).
-
D.
hasMusicalSettingsBy
Indicates that a work has been set to music or musically arranged by a specified creator or composer.
-
E.
hasMusicalArrangementCharacteristic
Indicates that a musical arrangement possesses a specific characteristic, feature, or quality.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 3, 2026, 4:31 p.m.