Triple
T35316253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prelude in D minor, BWV 850 |
E1019912
|
entity |
| Predicate | keyCategory |
P64612
|
FINISHED |
| Object | minor key |
—
|
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: minor key | Statement: [Prelude in D minor, BWV 850, keyCategory, minor key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyCategory Context triple: [Prelude in D minor, BWV 850, keyCategory, minor key]
-
A.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
B.
keyVariety
Indicates that one entity is a primary or defining type, form, or variant of another entity within a set or category.
-
C.
coreCategory
chosen
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
-
D.
keys
Indicates that one entity serves as a key (or set of keys) that can open, access, or control another entity.
-
E.
keyType
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f790918e2481908851ef7fa47f9d19 |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.