Triple
T32380717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violin Concerto in A minor, Op. 82 |
E827407
|
entity |
| Predicate | isAdmiredFor |
P135397
|
FINISHED |
| Object | lyrical expressiveness |
—
|
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: lyrical expressiveness | Statement: [Violin Concerto in A minor, Op. 82, isAdmiredFor, lyrical expressiveness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdmiredFor Context triple: [Violin Concerto in A minor, Op. 82, isAdmiredFor, lyrical expressiveness]
-
A.
isAdmiredBy
Indicates that one entity holds admiration or high regard for another entity.
-
B.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
celebratedAs
Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
-
D.
acclaimedFor
chosen
Indicates that an entity receives widespread praise or recognition specifically for another entity, such as a work, achievement, or contribution.
-
E.
isPraisedIn
Indicates that an entity receives praise, commendation, or positive recognition within a specified context or source.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:51 a.m.