Triple
T30106068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1952 Theater Piece No. 1 performance |
E765133
|
entity |
| Predicate | composerOfMusicalElements |
P40533
|
FINISHED |
| Object | John Cage |
—
|
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: John Cage | Statement: [1952 Theater Piece No. 1 performance, composerOfMusicalElements, John Cage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerOfMusicalElements Context triple: [1952 Theater Piece No. 1 performance, composerOfMusicalElements, John Cage]
-
A.
composedForMusicBy
Indicates that a musical work was specifically created or written by a particular composer.
-
B.
partOfComposerOeuvre
chosen
Indicates that a musical work belongs to and is included within the overall body of compositions created by a particular composer.
-
C.
usesMusicalElement
Indicates that one entity employs or incorporates a particular musical element (such as rhythm, melody, harmony, or timbre) in its composition, performance, or structure.
-
D.
coComposer
Indicates a relationship where two or more entities jointly compose a musical or artistic work together.
-
E.
hornComposition
Indicates the material or substance that an entity’s horn is made of.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 7:09 p.m.