Triple
T37381258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K. 492 |
E928436
|
entity |
| Predicate | hasFamousEnsemble |
P105232
|
FINISHED |
| Object | Sull’aria… che soave zeffiretto |
—
|
NE NERFINISHED |
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: Sull’aria… che soave zeffiretto | Statement: [K. 492, hasFamousEnsemble, Sull’aria… che soave zeffiretto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamousEnsemble Context triple: [K. 492, hasFamousEnsemble, Sull’aria… che soave zeffiretto]
-
A.
hasEnsembleCast
Indicates that a work features an ensemble cast, meaning multiple principal performers share roughly equal prominence rather than having a single clear lead.
-
B.
famousEnsemble
chosen
Indicates that the subject is a well-known group of performers or artists collectively recognized for their work.
-
C.
partOfCastEnsembleWith
Indicates that two or more performers are members of the same cast ensemble in a shared production.
-
D.
hasEnsembles
Indicates that an entity is associated with one or more ensembles, typically as a member, component, or participant.
-
E.
notableEnsemble
Indicates that an entity is a prominent or significant member of a particular group, band, or ensemble.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 3, 2026, 4:16 p.m.