Triple
T24042730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notation IV for solo piano |
E595428
|
entity |
| Predicate | expansionMedium |
P78290
|
FINISHED |
| Object | orchestra |
—
|
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: orchestra | Statement: [Notation IV for solo piano, expansionMedium, orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionMedium Context triple: [Notation IV for solo piano, expansionMedium, orchestra]
-
A.
applicableMedium
Indicates that a particular medium or material is suitable for use with, or can be effectively applied by, the referenced entity.
-
B.
usedMedium
Indicates that an action or communication was carried out through a particular medium or channel.
-
C.
propagationMedium
Indicates the medium or substance through which something (such as a signal, wave, or influence) is transmitted or propagated.
-
D.
representsMedium
Indicates that one entity serves as the medium, channel, or means through which another entity is expressed, communicated, or realized.
-
E.
subsequentMedium
chosen
Indicates that one medium or format follows another in a sequence, typically as a later or alternative form of the same content or communication.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8db3b4c81908a36eace8ec136cc |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:58 p.m.