Triple
T16696430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kid Cudi (Pissy Pamper) (leaked track) |
E405727
|
entity |
| Predicate | officialRelease |
P9940
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Kid Cudi (Pissy Pamper) (leaked track), officialRelease, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialRelease Context triple: [Kid Cudi (Pissy Pamper) (leaked track), officialRelease, no]
-
A.
publicRelease
Indicates that something is made available to the general public, typically after any private or restricted access period has ended.
-
B.
releaseStatus
chosen
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
-
C.
releasedSpecial
Indicates that an entity has issued or made available a special version, edition, or release of something.
-
D.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
E.
releaseType
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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37eadc35881909fb0cc405a0e2fae |
completed | April 18, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.