Triple
T23146179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonata for Tuba and Piano |
E577594
|
entity |
| Predicate | writtenForInstrumentFamily |
P151097
|
FINISHED |
| Object | brass |
—
|
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: brass | Statement: [Sonata for Tuba and Piano, writtenForInstrumentFamily, brass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenForInstrumentFamily Context triple: [Sonata for Tuba and Piano, writtenForInstrumentFamily, brass]
-
A.
primaryInstrumentFamily
Indicates the main family or category of musical instruments with which an entity is primarily associated.
-
B.
hasInstrumentFamily
Indicates that an instrument is associated with a particular family or category of instruments (e.g., strings, brass, woodwinds).
-
C.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
-
D.
designedInstrument
Indicates that an agent is responsible for creating or planning the design of a particular instrument.
-
E.
typeOfInstrument
Indicates the specific kind or category of instrument associated with an entity.
- 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ece211c81908b53e98f0acae09a |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:01 p.m.