Triple
T9491682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | String Octet in E-flat major, Op. 20 |
E228904
|
entity |
| Predicate | hasScherzoType |
P88912
|
FINISHED |
| Object | fairy-like, gossamer texture |
—
|
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: fairy-like, gossamer texture | Statement: [String Octet in E-flat major, Op. 20, hasScherzoType, fairy-like, gossamer texture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScherzoType Context triple: [String Octet in E-flat major, Op. 20, hasScherzoType, fairy-like, gossamer texture]
-
A.
hasScherzo
Indicates that something (typically a musical work or movement) includes or is associated with a scherzo section or component.
-
B.
hasScherzoMovement
Indicates that a musical work includes a scherzo as one of its movements.
-
C.
scherzoKey
Indicates the musical key in which the scherzo section of a composition is written.
-
D.
hasOrchestraType
Indicates that an entity is associated with, or classified by, a specific type or category of orchestra.
-
E.
hasHumorType
Indicates that an entity possesses or is characterized by a particular style, category, or type of humor.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd80c89ec48190a2ad49394cab9c56 |
completed | April 1, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca8c6b0f081908334d6c7cf80e03c |
completed | April 1, 2026, 5:10 a.m. |
Created at: March 30, 2026, 7:56 p.m.