Triple
T23839756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carmen Arcadiae Mechanicae Perpetuum |
E590952
|
entity |
| Predicate | isOrchestralWorkBy |
P153834
|
FINISHED |
| Object | Harrison Birtwistle |
—
|
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: Harrison Birtwistle | Statement: [Carmen Arcadiae Mechanicae Perpetuum, isOrchestralWorkBy, Harrison Birtwistle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOrchestralWorkBy Context triple: [Carmen Arcadiae Mechanicae Perpetuum, isOrchestralWorkBy, Harrison Birtwistle]
-
A.
isOrchestral
Indicates that something involves, is written for, or is performed by an orchestra.
-
B.
isLastOrchestralWorkOf
Indicates that the work is the final orchestral composition created by the specified composer or creator.
-
C.
performedWithOrchestra
Indicates that a performance or musical work was carried out in collaboration with an orchestra.
-
D.
musicOrchestratedBy
Indicates that a piece of music or musical work is arranged or orchestrated by a specific person or entity.
-
E.
hasOrchestralSuite
Indicates that a musical work is associated with, or has been arranged into, an orchestral suite derived from it.
- F. None of above. chosen
Provenance (4 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c886aab081909ad896abe383afb9 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 8:08 p.m.