Triple
T24201910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olimpiade |
E600003
|
entity |
| Predicate | widelySetToMusicBy |
P78347
|
FINISHED |
| Object | Antonio Caldara |
—
|
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: Antonio Caldara | Statement: [Olimpiade, widelySetToMusicBy, Antonio Caldara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widelySetToMusicBy Context triple: [Olimpiade, widelySetToMusicBy, Antonio Caldara]
-
A.
isOftenSungToTune
Indicates that one song or piece of text is frequently performed using the melody or musical setting of another.
-
B.
songMadeFamousBy
Indicates that a song became widely known or popular primarily through the performance, recording, or promotion of a particular artist or group.
-
C.
notableSongWrittenFor
Indicates that a particular song was specifically written for a given person, group, work, event, or purpose.
-
D.
isPopularSongOf
Indicates that a song is widely liked, well-known, or frequently enjoyed in relation to a particular entity (such as an artist, album, or context).
-
E.
setToMusicAs
chosen
Indicates that one entity (typically a text or work) has been adapted and arranged by another entity into a musical composition.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca1f3b481908c14052a8435fd21 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.