Triple
T13230020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugue in F major, BWV 856 |
E314987
|
entity |
| Predicate | hasTuningConcept |
P531
|
FINISHED |
| Object | well temperament |
—
|
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: well temperament | Statement: [Fugue in F major, BWV 856, hasTuningConcept, well temperament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTuningConcept Context triple: [Fugue in F major, BWV 856, hasTuningConcept, well temperament]
-
A.
tuning
Indicates the adjustment or calibration of something’s parameters or settings to achieve desired performance or behavior.
-
B.
tuningMethod
Indicates the method or approach used to adjust or optimize something’s parameters or performance.
-
C.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
D.
isTunedTo
Indicates that one entity has been adjusted or configured to operate at, receive, or correspond to the frequency, channel, or setting of another entity.
-
E.
tunedBy
Indicates that one entity has been adjusted or calibrated in its settings, parameters, or configuration by another entity.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d336ae08190bfc118cfbefddf84 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:21 p.m.