Triple
T38188486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christoph Graupner |
E1005384
|
entity |
| Predicate | hasPartInOeuvre |
P40533
|
FINISHED |
| Object | orchestral suites |
—
|
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: orchestral suites | Statement: [Christoph Graupner, hasPartInOeuvre, orchestral suites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartInOeuvre Context triple: [Christoph Graupner, hasPartInOeuvre, orchestral suites]
-
A.
partOfArtistOeuvre
Indicates that something (such as a work or piece) belongs to and is included within an artist’s overall body of work.
-
B.
hasPartInWrittenWork
Indicates that an entity participates in or contributes to the creation of a written work.
-
C.
hasPartInCreativeOutput
Indicates that an entity contributed a component, role, or involvement to the creation or production of a particular creative work.
-
D.
isPartOfBodyOfWork
Indicates that one creative work is a component, segment, or installment within a larger overarching body of related work.
-
E.
partOfComposerOeuvre
chosen
Indicates that a musical work belongs to and is included within the overall body of compositions created by a particular composer.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00776c4ebc8190899005fda34234d5 |
completed | May 10, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_6a0076f8a4c4819093ed577e67aa38f9 |
completed | May 10, 2026, 12:15 p.m. |
Created at: May 3, 2026, 4:29 p.m.