Triple
T22322377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violin Concerto in G major, Op. 4 No. 3, RV 301 |
E551817
|
entity |
| Predicate | workNumberInRVcatalog |
P85806
|
FINISHED |
| Object | 301 |
—
|
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: 301 | Statement: [Violin Concerto in G major, Op. 4 No. 3, RV 301, workNumberInRVcatalog, 301]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInRVcatalog Context triple: [Violin Concerto in G major, Op. 4 No. 3, RV 301, workNumberInRVcatalog, 301]
-
A.
workCatalogueNumber
Indicates the catalog or reference number assigned to a specific work within an organized catalogue or listing.
-
B.
workCatalogueNumberOfWork
chosen
Indicates the catalogue number assigned to a specific work within a cataloging or classification system.
-
C.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
D.
workNumberInOpus8
Indicates that a work is assigned a specific number within Opus 8 of a composer’s catalog.
-
E.
workNumberInDeRePublica
Indicates that an entity has a specific work number or index within the collection or edition of "De Re Publica."
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15765a004819081dcdccbfd0efea7 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.