Triple
T37304600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Six Sonatas for Keyboard, Wq 49 |
E926042
|
entity |
| Predicate | hasTypeOfForm |
P16808
|
FINISHED |
| Object | multi-movement sonata cycle |
—
|
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: multi-movement sonata cycle | Statement: [Six Sonatas for Keyboard, Wq 49, hasTypeOfForm, multi-movement sonata cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfForm Context triple: [Six Sonatas for Keyboard, Wq 49, hasTypeOfForm, multi-movement sonata cycle]
-
A.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
B.
hasFormFor
Indicates that one entity possesses or provides a specific form or document intended to be used by another entity or for a particular purpose.
-
C.
hasFormulationType
Indicates the specific way something is physically prepared or presented, such as its dosage form, composition, or delivery format.
-
D.
hasTypeOfCase
Indicates that an entity is associated with or classified under a particular type or category of case.
-
E.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
Created at: May 3, 2026, 4:16 p.m.