Triple
T25083215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gianetta |
E628239
|
entity |
| Predicate | hasComposerOfWork |
P151822
|
FINISHED |
| Object | music by Arthur Sullivan |
—
|
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: music by Arthur Sullivan | Statement: [Gianetta, hasComposerOfWork, music by Arthur Sullivan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComposerOfWork Context triple: [Gianetta, hasComposerOfWork, music by Arthur Sullivan]
-
A.
hasComposerPreviousWork
Indicates that a composer has created an earlier work prior to the current one.
-
B.
isRelatedWorkOfComposer
chosen
Indicates that one work is associated with or connected to a particular composer, typically as a composition created by that composer.
-
C.
hasCoComposer
Indicates that an entity shares authorship of a musical composition with one or more other composers.
-
D.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
E.
hasComposerInResidence
Indicates that an organization or institution has officially appointed a specific composer to serve in a resident or ongoing compositional role.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 18, 2026, 6:22 a.m.