Triple
T32661170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | As If by Design |
E835013
|
entity |
| Predicate | hasMusicBrainzWorkType |
P10647
|
FINISHED |
| Object | song |
—
|
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: song | Statement: [As If by Design, hasMusicBrainzWorkType, song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicBrainzWorkType Context triple: [As If by Design, hasMusicBrainzWorkType, song]
-
A.
hasMusicalWorkType
Indicates that a musical work is associated with a specific type or category of musical composition.
-
B.
isMusicalWork
Indicates that one entity is a musical composition or piece created as an artistic work.
-
C.
musicBrainzID
Indicates that an entity is associated with a specific identifier in the MusicBrainz database that uniquely references it.
-
D.
musicBrainzType
chosen
Indicates the specific MusicBrainz-defined category or classification assigned to an entity within the MusicBrainz database.
-
E.
isMusicalWorkFor
Indicates that a musical work is created, intended, or designated for a particular entity, such as an instrument, performer, event, or context.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 1:08 a.m.