Triple
T23620013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suite No. 3 for Tuba |
E583289
|
entity |
| Predicate | writtenForInstrument |
P153299
|
FINISHED |
| Object | tuba |
—
|
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: tuba | Statement: [Suite No. 3 for Tuba, writtenForInstrument, tuba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenForInstrument Context triple: [Suite No. 3 for Tuba, writtenForInstrument, tuba]
-
A.
writtenForInstrumentFamily
Indicates that a musical work is composed or arranged specifically to be performed by a particular family of instruments.
-
B.
designedInstrument
Indicates that an agent is responsible for creating or planning the design of a particular instrument.
-
C.
writtenForPerformer
Indicates that a work was specifically composed or created to be performed by a particular performer or type of performer.
-
D.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
-
E.
instrumentalIn
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
- 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_69e248fbcd9081908ba08913f9d30826 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17780a88190b6f0d6d551133454 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f138b8c9248190b059bc38a9a50958 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 17, 2026, 6:45 p.m.