Triple
T22124406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baal Shem |
E546754
|
entity |
| Predicate | premiereInstrument |
P99288
|
FINISHED |
| Object | violin |
—
|
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: violin | Statement: [Baal Shem, premiereInstrument, violin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiereInstrument Context triple: [Baal Shem, premiereInstrument, violin]
-
A.
premiereSoloist
Indicates that an entity serves as the primary featured solo performer in a particular performance or production.
-
B.
premiereForm
Indicates that an artistic or media work is presented or performed publicly for the first time in a particular form or version.
-
C.
parentInstrument
Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
-
D.
typicalInstrumentAtPremiere
chosen
Indicates that a particular musical instrument is commonly used or featured during the premiere performance of a work.
-
E.
instrument
Indicates that an action is carried out using a particular tool, means, or implement as its instrument.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1298016e081909d00015ca516d9fd |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.