Triple
T25198514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Blood and Crescent Moon |
E631065
|
entity |
| Predicate | hasComposerBackground |
P72668
|
FINISHED |
| Object | rock drummer and songwriter |
—
|
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: rock drummer and songwriter | Statement: [Holy Blood and Crescent Moon, hasComposerBackground, rock drummer and songwriter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComposerBackground Context triple: [Holy Blood and Crescent Moon, hasComposerBackground, rock drummer and songwriter]
-
A.
hasComposerPreviousWork
Indicates that a composer has created an earlier work prior to the current one.
-
B.
hasAuthorBackgroundIn
chosen
Indicates that an author possesses a particular background, such as education, experience, or expertise, in a specified field or domain.
-
C.
hasComposerInResidence
Indicates that an organization or institution has officially appointed a specific composer to serve in a resident or ongoing compositional role.
-
D.
hasCoComposer
Indicates that an entity shares authorship of a musical composition with one or more other composers.
-
E.
hasArrangerBackground
Indicates that an entity has a background or experience in musical arranging.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 21, 2026, 12:50 p.m.