Triple
T37611395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarinet Trio in A minor, Op. 114 |
E935792
|
entity |
| Predicate | hasStringInstrument |
P195245
|
FINISHED |
| Object | cello |
—
|
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: cello | Statement: [Clarinet Trio in A minor, Op. 114, hasStringInstrument, cello]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStringInstrument Context triple: [Clarinet Trio in A minor, Op. 114, hasStringInstrument, cello]
-
A.
hasMusicalInstrument
Indicates that one entity possesses, uses, or is associated with a particular musical instrument.
-
B.
hasMusicalInstruments
chosen
Indicates that one entity possesses, includes, or is associated with one or more musical instruments.
-
C.
hadInstrument
Indicates that an action or event was performed using a particular instrument or tool.
-
D.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
E.
hasKeyInstrumentalist
Indicates that an entity (such as a musical work or performance) has a primary or featured instrumental performer associated with it.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00868083b081909afc3d8d4ad56b43 |
completed | May 10, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_6a0084f5f72c8190b08afa82690e322a |
completed | May 10, 2026, 1:15 p.m. |
Created at: May 3, 2026, 4:18 p.m.