Triple
T34331103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dido and Aeneas (Mark Morris production) |
E881008
|
entity |
| Predicate | musicPeriodOfSource |
P33181
|
FINISHED |
| Object | Baroque |
—
|
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: Baroque | Statement: [Dido and Aeneas (Mark Morris production), musicPeriodOfSource, Baroque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicPeriodOfSource Context triple: [Dido and Aeneas (Mark Morris production), musicPeriodOfSource, Baroque]
-
A.
timePeriodOfMusic
chosen
Indicates the historical or stylistic time period during which a piece of music was created, popular, or characteristic.
-
B.
musicMotif
Indicates a recurring musical idea, theme, or pattern that appears multiple times within a composition or across related works.
-
C.
musicSource
Indicates that one entity serves as the origin or provider of music for another entity or context.
-
D.
musicFeatured
Indicates that a particular piece of music is prominently included or used within another work, event, or context.
-
E.
musicField
Indicates a relationship where an entity is associated with a particular field, genre, or domain within music.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 1, 2026, 1:58 a.m.