Triple
T30487542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoso |
E775760
|
entity |
| Predicate | hasLiveReleases |
P21537
|
FINISHED |
| Object | live recordings included on Elements |
—
|
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: live recordings included on Elements | Statement: [Yoso, hasLiveReleases, live recordings included on Elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveReleases Context triple: [Yoso, hasLiveReleases, live recordings included on Elements]
-
A.
hasLiveSingleRelease
Indicates that an entity has released a live recording of a single as an official release.
-
B.
hasLiveAlbumReleaseType
Indicates that a musical work or recording has a release type specifically classified as a live album.
-
C.
hasAlbumRelease
Indicates that an entity (typically an artist or band) has released a specific music album.
-
D.
hasLiveAlbum
chosen
Indicates that an artist or musical act has released at least one live album recording.
-
E.
hasAudioReleases
Indicates that an entity has associated audio-format releases (such as recordings, tracks, or audio editions) that have been published or made available.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 29, 2026, 8:13 p.m.