Triple
T37359755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata in F-sharp minor, Op. 81 |
E927545
|
entity |
| Predicate | isSubstantialWork |
P188307
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Piano Sonata in F-sharp minor, Op. 81, isSubstantialWork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubstantialWork Context triple: [Piano Sonata in F-sharp minor, Op. 81, isSubstantialWork, true]
-
A.
hasSignificantWorkType
Indicates that an entity is associated with a primary or notably important type or category of work.
-
B.
hasMajorWork
Indicates that an entity (typically a person, creator, or organization) is associated with a significant or principal work they produced or are best known for.
-
C.
hasSubsequentWork
Indicates that one work is followed by another work that continues, succeeds, or builds upon it in sequence.
-
D.
hasWorkAsSubject
Indicates that an entity serves as the subject (creator or originator) of a particular work or creative output.
-
E.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:16 p.m.