Triple
T34490699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto No. 2 |
E885457
|
entity |
| Predicate | openingCharacteristic |
P180649
|
FINISHED |
| Object | improvisatory piano solo |
—
|
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: improvisatory piano solo | Statement: [Piano Concerto No. 2, openingCharacteristic, improvisatory piano solo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingCharacteristic Context triple: [Piano Concerto No. 2, openingCharacteristic, improvisatory piano solo]
-
A.
openingMechanism
Indicates the method or mechanism by which an object or structure is opened or made accessible.
-
B.
openingThemeCharacteristic
chosen
Indicates that a specified attribute or quality characterizes the opening theme of a work.
-
C.
openingStyle
Indicates how something is initially presented, introduced, or begun in terms of manner, format, or approach.
-
D.
openingCharacter
Indicates that one entity is the first character or symbol at the beginning of another entity (such as a string, word, or text).
-
E.
openingSettingOf
Indicates that one entity serves as the initial or first setting/location in which the other entity begins or is introduced.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 1, 2026, 2:01 a.m.