Triple
T26266584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | works of Wolfgang Amadeus Mozart |
E656998
|
entity |
| Predicate | languageOfVocalWorks |
P47965
|
FINISHED |
| Object | Italian |
—
|
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: Italian | Statement: [works of Wolfgang Amadeus Mozart, languageOfVocalWorks, Italian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfVocalWorks Context triple: [works of Wolfgang Amadeus Mozart, languageOfVocalWorks, Italian]
-
A.
vocalVersionLanguage
Indicates the language in which the vocal performance or sung lyrics of a work are expressed.
-
B.
languageOfVocalization
chosen
Indicates the language in which a vocalization (such as speech or singing) is produced.
-
C.
hasVocalLanguageMix
Indicates that an entity’s vocal communication combines multiple languages or language varieties within its speech.
-
D.
languageOfWritings
Indicates that a specified language is the one in which certain writings or written works are composed.
-
E.
languageOfUnderlyingWork
Indicates the language in which the original or underlying work (from which a derived or related work stems) is expressed.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 26, 2026, 9:11 p.m.