Triple
T34490700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto No. 2 |
E885457
|
entity |
| Predicate | closingCharacteristic |
P124939
|
FINISHED |
| Object | brilliant virtuosic finale |
—
|
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: brilliant virtuosic finale | Statement: [Piano Concerto No. 2, closingCharacteristic, brilliant virtuosic finale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closingCharacteristic Context triple: [Piano Concerto No. 2, closingCharacteristic, brilliant virtuosic finale]
-
A.
closingMovementCharacter
Indicates a characteristic or quality of the movement involved in closing something (e.g., how the closing action is performed or behaves).
-
B.
closingFeatures
Indicates that an entity has specific characteristics, terms, or attributes associated with the act or process of closing (e.g., ending, shutting down, or finalizing something).
-
C.
closingDevice
Indicates that an entity functions to close, seal, or shut another entity, such as an opening, container, or mechanism.
-
D.
closingSettingOf
Indicates the setting, condition, or context in which a closing or ending event takes place.
-
E.
closingSequenceFeature
chosen
Indicates a feature or element that appears specifically in the closing sequence of an event, process, or media item.
- 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_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.