Triple
T38599406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozart–Da Ponte trilogy |
E934167
|
entity |
| Predicate | catalogueAbbreviationOfComposer |
P191868
|
FINISHED |
| Object | K. |
—
|
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: K. | Statement: [Mozart–Da Ponte trilogy, catalogueAbbreviationOfComposer, K.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueAbbreviationOfComposer Context triple: [Mozart–Da Ponte trilogy, catalogueAbbreviationOfComposer, K.]
-
A.
catalogueOfComposer
Indicates that one entity is a catalogue that systematically lists or documents the works of a particular composer.
-
B.
collectiveNameForComposers
Indicates a term that denotes a group or category of composers collectively.
-
C.
realNameOfComposer
Indicates that the object is the actual, full real-world name of the composer referred to by the subject.
-
D.
composerOfCataloguedWork
Indicates that one entity is the composer or creator of a specific catalogued musical or artistic work associated with another entity.
-
E.
notableComposerOfType
Indicates that an entity is a well-known or distinguished composer associated with a specified type, category, or genre of composition.
- F. None of above. chosen
Provenance (4 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: May 3, 2026, 4:32 p.m.