Triple
T23227750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Requiem in D minor, Op. 48 |
E581058
|
entity |
| Predicate | instrumentationVersion |
P1149
|
FINISHED |
| Object | chamber orchestra and organ |
—
|
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: chamber orchestra and organ | Statement: [Requiem in D minor, Op. 48, instrumentationVersion, chamber orchestra and organ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentationVersion Context triple: [Requiem in D minor, Op. 48, instrumentationVersion, chamber orchestra and organ]
-
A.
hasInstrumentVersion
Indicates that an entity is associated with a specific version or variant of an instrument used in its creation, performance, or measurement.
-
B.
hasInstrumentationProvidedBy
Indicates that the instrumentation used in an activity, process, or work is supplied or made available by a specified provider.
-
C.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
-
D.
typicalInstrumentation
chosen
Indicates the usual or standard set of instruments commonly associated with performing or realizing something (such as a work, genre, or piece).
-
E.
finalVersionInstrumentation
Indicates that the instrumentation or monitoring setup applies specifically to the final, released version of a system or artifact.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922f5b4081908145d66ea7534493 |
completed | April 29, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.