Triple
T29528379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonatina in C major, Op. 36 No. 1 |
E749128
|
entity |
| Predicate | hasRecapitulation |
P189573
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sonatina in C major, Op. 36 No. 1, hasRecapitulation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecapitulation Context triple: [Sonatina in C major, Op. 36 No. 1, hasRecapitulation, yes]
-
A.
recapitulationFeature
chosen
Indicates that one entity serves as a summarizing or restating feature that revisits or reiterates key aspects of another entity.
-
B.
hasReprise
Indicates that an action, theme, or element is repeated or returns after its initial occurrence.
-
C.
hasRe-recording
Indicates that one recording is a new or updated version made again from the same original material or performance.
-
D.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
-
E.
hasReplay
Indicates that an event, action, or interaction is available to be viewed or experienced again in a recorded or reconstructed form.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: April 28, 2026, 4:49 p.m.