Triple
T23880747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Got That Work |
E600193
|
entity |
| Predicate | featuresLabelSound |
P154319
|
FINISHED |
| Object | Cash Money Records |
—
|
NE NERFINISHED |
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: Cash Money Records | Statement: [I Got That Work, featuresLabelSound, Cash Money Records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresLabelSound Context triple: [I Got That Work, featuresLabelSound, Cash Money Records]
-
A.
featuresVocal
Indicates that one entity includes or presents the vocal performance or voice of another entity.
-
B.
labelFeatures
Indicates assigning descriptive tags or identifiers to specific features or attributes of an entity.
-
C.
featuresVocalPercussion
Indicates that the subject includes or makes use of vocal percussion (such as beatboxing or mouth-made rhythmic sounds) as part of its content or performance.
-
D.
notableSoundCharacteristic
Indicates a distinctive or noteworthy quality of the sound produced or associated with an entity.
-
E.
featuresSample
Indicates that an entity includes or presents a particular sample as one of its components or examples.
- F. None of above. chosen
Provenance (4 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cc05226c8190aa640b6a89cb3ed3 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:24 p.m.