Triple
T3127910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Use This Gospel |
E65340
|
entity |
| Predicate | albumTypeContext |
P25507
|
FINISHED |
| Object | studio album |
—
|
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: studio album | Statement: [Use This Gospel, albumTypeContext, studio album]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: albumTypeContext Context triple: [Use This Gospel, albumTypeContext, studio album]
-
A.
musicAlbum
Indicates that there is a relationship where an entity is a music album associated with another entity, such as an artist or release.
-
B.
albumGenre
Indicates that a musical album belongs to or is categorized under a particular genre.
-
C.
studioAlbum
chosen
Indicates that the subject is a studio-recorded album created and released by the object (typically an artist or band).
-
D.
conceptAlbum
Indicates that a musical work is a concept album, meaning its tracks are thematically or narratively unified around a central idea or story.
-
E.
musicBrainzType
Indicates the specific MusicBrainz-defined category or classification assigned to an entity within the MusicBrainz database.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada546a6648190bc4bc3e599e6aa95 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.