Triple
T29029075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Introduzione: Un poco adagio – Allegro vivace |
E737676
|
entity |
| Predicate | partOfOpus |
P131077
|
FINISHED |
| Object | Op. 11 |
—
|
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: Op. 11 | Statement: [Introduzione: Un poco adagio – Allegro vivace, partOfOpus, Op. 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfOpus Context triple: [Introduzione: Un poco adagio – Allegro vivace, partOfOpus, Op. 11]
-
A.
hasPartInCreativeOutput
Indicates that an entity contributed a component, role, or involvement to the creation or production of a particular creative work.
-
B.
isPartOfBodyOfWork
chosen
Indicates that one creative work is a component, segment, or installment within a larger overarching body of related work.
-
C.
partOfWorkType
Indicates that something is a component, subtype, or specific category within a broader type of work.
-
D.
partOfBook
Indicates that one entity is a component or section contained within a larger book entity.
-
E.
hasNumberOfPartsInWholeWork
Indicates that an entity specifies how many component parts are contained within a complete work.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: April 28, 2026, 9:54 a.m.