Triple
T22384728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RV 297 (Winter) |
E553364
|
entity |
| Predicate | workTypeWithinCollection |
P2011
|
FINISHED |
| Object | seasonal concerto |
—
|
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: seasonal concerto | Statement: [RV 297 (Winter), workTypeWithinCollection, seasonal concerto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workTypeWithinCollection Context triple: [RV 297 (Winter), workTypeWithinCollection, seasonal concerto]
-
A.
workCollectedBy
Indicates that a created work has been gathered, acquired, or included within a collection maintained by another entity.
-
B.
basedOnWorkCollection
Indicates that something is derived from, adapted from, or otherwise created using a particular collection of works as its source or foundation.
-
C.
hasWorkInCollection
chosen
Indicates that a work or item is included as part of a particular collection.
-
D.
hasRoleInWorkType
Indicates that an entity holds a specific role or function within a particular type or category of work.
-
E.
workCollectionTitle
Indicates the title assigned to a collection of works associated with an entity.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582e58dc8190a2ad6b10c9d1f951 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.