Triple
T12680117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suite for Piano, Op. 25 |
E302921
|
entity |
| Predicate | usesRow |
P26269
|
FINISHED |
| Object | single basic twelve-tone row |
—
|
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: single basic twelve-tone row | Statement: [Suite for Piano, Op. 25, usesRow, single basic twelve-tone row]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRow Context triple: [Suite for Piano, Op. 25, usesRow, single basic twelve-tone row]
-
A.
usedRite
Indicates that an entity performed, followed, or applied a particular rite or ritual in some context.
-
B.
usesForm
chosen
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
-
C.
usedCross
Indicates that one entity made use of a cross-shaped object or structure, or traversed by means of a crossing point such as a crosswalk or intersection.
-
D.
usesDRS
Indicates that one entity employs or relies on a specific Decision Review System (DRS) for evaluation, verification, or decision-making purposes.
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961b32dbc81908101fc5f07e26ed3 |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.