Triple
T22070404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schelomo |
E545389
|
entity |
| Predicate | placeInCelloRepertoire |
P3738
|
FINISHED |
| Object | standard 20th-century concerto-like work |
—
|
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: standard 20th-century concerto-like work | Statement: [Schelomo, placeInCelloRepertoire, standard 20th-century concerto-like work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInCelloRepertoire Context triple: [Schelomo, placeInCelloRepertoire, standard 20th-century concerto-like work]
-
A.
hasPrincipalCello
Indicates that an entity has another entity serving as its principal cello performer or leader of the cello section.
-
B.
placeInBachCatalog
Indicates the position or entry number that a musical work occupies within the Bach catalog.
-
C.
repertoireIncludes
chosen
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
D.
partOfComposerOeuvre
Indicates that a musical work belongs to and is included within the overall body of compositions created by a particular composer.
-
E.
notabilityInRepertoire
Indicates that a work holds particular significance or prominence within an entity’s repertoire.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128881af481909b28cda2d343f4e3 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.