Triple
T29241377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheik Yerbouti |
E741323
|
entity |
| Predicate | containsStudioOverdubs |
P78805
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sheik Yerbouti, containsStudioOverdubs, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsStudioOverdubs Context triple: [Sheik Yerbouti, containsStudioOverdubs, true]
-
A.
usesVocalOverdubbing
chosen
Indicates that one entity applies vocal overdubbing to another entity, layering additional recorded vocals over an existing audio track.
-
B.
hasStudioOuttake
Indicates that there exists an alternate, typically unreleased or non-final studio recording associated with the referenced work or session.
-
C.
hasStudioRecordings
Indicates that one entity possesses or is associated with studio-made audio recordings of another entity.
-
D.
hasStudioRecordingComponent
Indicates that one entity is a studio recording component or part of another entity.
-
E.
basedOnStudioRecording
Indicates that something (such as a work, version, or performance) is derived from, adapted from, or created using a particular studio recording as its source.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: April 28, 2026, 12:31 p.m.