Triple
T31861045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Whisper |
E813326
|
entity |
| Predicate | hasCompositionElement |
P204108
|
FINISHED |
| Object | dynamic shifts |
—
|
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: dynamic shifts | Statement: [A Whisper, hasCompositionElement, dynamic shifts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompositionElement Context triple: [A Whisper, hasCompositionElement, dynamic shifts]
-
A.
hasCompositionBy
Indicates that something (such as a work or piece) is composed or created by a particular composer or author.
-
B.
hasCompositionType
Indicates that one entity is composed of or formed by another entity in a specific structural or material way.
-
C.
hasPanelComposition
Indicates that something is composed of or structured into multiple panels or panel-like sections.
-
D.
isComposedIn
Indicates that something is created, written, or formed within a particular context, medium, or framework.
-
E.
hasExtendedCompositions
Indicates that an entity creates, contains, or is associated with compositions that are longer or more elaborate than standard or typical works.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a032616547c8190bc877202e43403eb |
completed | May 12, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_6a0325246abc819088e16a7fbadf40c5 |
completed | May 12, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_6a032615ac7c81908c917e1be93c1189 |
completed | May 12, 2026, 1:07 p.m. |
Created at: April 30, 2026, 11:53 p.m.