Triple
T28145163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godchild |
E714457
|
entity |
| Predicate | releaseTypeOfNotableRecording |
P3286
|
FINISHED |
| Object | studio recording |
—
|
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 recording | Statement: [Godchild, releaseTypeOfNotableRecording, studio recording]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseTypeOfNotableRecording Context triple: [Godchild, releaseTypeOfNotableRecording, studio recording]
-
A.
notableArtistRelease
Indicates that a release (such as an album, single, or work) is created or issued by an artist who is considered notable or prominent.
-
B.
releasedMusicBy
Indicates that a musical work (such as a song, album, or EP) was issued or made publicly available by a particular artist or musical act.
-
C.
releasedSong
Indicates that an artist or entity has made a particular song publicly available, typically as a publication or distribution event.
-
D.
notableRelease
Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with another entity.
-
E.
releaseType
chosen
Indicates the kind or category of a release event or version associated with an entity.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 9:56 p.m.