Triple
T34490713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto No. 2 |
E885457
|
entity |
| Predicate | isPopularInRepertoire |
P105958
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Piano Concerto No. 2, isPopularInRepertoire, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularInRepertoire Context triple: [Piano Concerto No. 2, isPopularInRepertoire, yes]
-
A.
includedInStandardRepertoire
chosen
Indicates that something is part of the commonly accepted or regularly used set within a particular standard repertoire.
-
B.
notabilityInRepertoire
Indicates that a work holds particular significance or prominence within an entity’s repertoire.
-
C.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
-
D.
isOftenPlayedBy
Indicates that one entity frequently performs, interprets, or executes another entity, such as a musician often playing a particular piece or instrument.
-
E.
isPopularRecordingOf
Indicates that one entity is a widely known or frequently enjoyed version or performance of another work, such as a song or composition.
- 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.