Triple
T24007860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notation III for solo piano |
E594438
|
entity |
| Predicate | basedOnSeriesType |
P93688
|
FINISHED |
| Object | 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: twelve-tone row | Statement: [Notation III for solo piano, basedOnSeriesType, twelve-tone row]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnSeriesType Context triple: [Notation III for solo piano, basedOnSeriesType, twelve-tone row]
-
A.
basedOnType
chosen
Indicates that one entity is derived, determined, or classified according to the type or category of another entity.
-
B.
basedOnSeriesConceptBy
Indicates that something is derived from or created using a series concept developed by a specified source.
-
C.
seriesType
Indicates the classification or category of a series that an entity belongs to or is associated with.
-
D.
belongsToTypeSeries
Indicates that something is a member or instance of a particular type series or classification series.
-
E.
basedInSeriesSetting
Indicates that something (such as a work, event, or element) is situated within or occurs in the primary setting established by a particular series.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d46ba1f88190a204d8cfb0f64be6 |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.