Triple
T37360031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inventions and Sinfonias |
E927552
|
entity |
| Predicate | containsWorkInEveryKey |
P203532
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Inventions and Sinfonias, containsWorkInEveryKey, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsWorkInEveryKey Context triple: [Inventions and Sinfonias, containsWorkInEveryKey, no]
-
A.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
B.
hasKeyOfWork
Indicates that one entity possesses or is associated with the key (tonal center) in which a work (such as a musical composition) is set.
-
C.
isInCollectionOfAllKeys
Indicates that something belongs to, or is a member of, the complete set of keys defined within a given context or structure.
-
D.
isContainedInWorkBy
Indicates that something is included within, or forms a part of, a larger work created by a specified agent.
-
E.
hasWorkInCollection
Indicates that a work or item is included as part of a particular collection.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a019d1407588190b3b9b83fca2e61fe |
completed | May 11, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a019c760e3081909cfe9c0603727e48 |
completed | May 11, 2026, 9:08 a.m. |
| PDg | Predicate description generation | batch_6a019d12c1208190940abb0736c389b0 |
completed | May 11, 2026, 9:10 a.m. |
Created at: May 3, 2026, 4:16 p.m.