Triple
T37844169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saffi |
E943557
|
entity |
| Predicate | belongsToWorkByComposer |
P151822
|
FINISHED |
| Object | Johann Strauss II |
—
|
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: Johann Strauss II | Statement: [Saffi, belongsToWorkByComposer, Johann Strauss II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToWorkByComposer Context triple: [Saffi, belongsToWorkByComposer, Johann Strauss II]
-
A.
isRelatedWorkOfComposer
chosen
Indicates that one work is associated with or connected to a particular composer, typically as a composition created by that composer.
-
B.
followsWorkOfComposer
Indicates that one entity creates or performs music in a style or tradition that continues or is influenced by the work of a particular composer.
-
C.
followedByWorkOfComposer
Indicates that one work or performance is immediately succeeded by a work created by a specified composer.
-
D.
followedByInComposerWork
Indicates that one element in a composer's work directly succeeds another in sequence within that same composition.
-
E.
dedicatedComposerWork
Indicates that a particular work was specifically created or formally dedicated by the composer to a person, group, or entity.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: May 3, 2026, 4:19 p.m.