Triple
T22437504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonatas, Op. 2 |
E554663
|
entity |
| Predicate | dedicateeRole |
P148181
|
FINISHED |
| Object | English patron of Clementi |
—
|
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: English patron of Clementi | Statement: [Piano Sonatas, Op. 2, dedicateeRole, English patron of Clementi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicateeRole Context triple: [Piano Sonatas, Op. 2, dedicateeRole, English patron of Clementi]
-
A.
dedicatee
Indicates the person or entity to whom a work, such as a book, artwork, or performance, is formally dedicated.
-
B.
dedicateeGroup
Indicates that an action, work, or resource is formally dedicated or addressed to a specific group of recipients.
-
C.
dedicateeTitle
Indicates the formal title or honorific held by the person to whom something (such as a work or object) is dedicated.
-
D.
dedicationBy
Indicates that one entity formally dedicates, commits, or devotes another entity (such as a work, resource, or effort) to a particular person, purpose, or cause.
-
E.
dedicationType
Indicates the specific kind or category of dedication that characterizes the relationship or action between entities.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15adf52f08190a5b592be3e68af0f |
completed | April 29, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:47 p.m.