Triple
T22979125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonata No. 6 in G minor, Op. 2 |
E571409
|
entity |
| Predicate | continuoInstruments |
P72278
|
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: [Sonata No. 6 in G minor, Op. 2, continuoInstruments, cello]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuoInstruments Context triple: [Sonata No. 6 in G minor, Op. 2, continuoInstruments, cello]
-
A.
instruments
Indicates that an agent uses a tool, device, or means to carry out an action or achieve an effect.
-
B.
instrumentsUsedBy
Indicates that a particular instrument, tool, or device is employed or utilized by a given entity to perform an action or achieve a result.
-
C.
designedInstrument
Indicates that an agent is responsible for creating or planning the design of a particular instrument.
-
D.
coInstrumentWith
Indicates that two or more entities are used together as instruments or means to perform the same action or achieve the same outcome.
-
E.
includesInstruments
chosen
Indicates that one entity contains, involves, or makes use of one or more instruments as part of its composition or execution.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18293f830819095cca91af7abd742 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.