Triple
T2797715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Well-Tempered Clavier |
E53077
|
entity |
| Predicate | keyCoverage |
P43234
|
FINISHED |
| Object | all 24 major and minor keys |
—
|
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: all 24 major and minor keys | Statement: [The Well-Tempered Clavier, keyCoverage, all 24 major and minor keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyCoverage Context triple: [The Well-Tempered Clavier, keyCoverage, all 24 major and minor keys]
-
A.
mayCoverArea
Indicates that one entity is permitted or able to extend over, include, or encompass a specified spatial area.
-
B.
providesCoverage
Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
-
C.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
D.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
E.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
- F. None of above. chosen
Provenance (4 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddf204148190a53f3f30d645d94c |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddcc348081908b5f760899389d4f |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 9:58 p.m.