Triple
T13940872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papa Don't Take No Mess |
E335246
|
entity |
| Predicate | samplingUsage |
P13406
|
FINISHED |
| Object | widely sampled in hip hop |
—
|
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: widely sampled in hip hop | Statement: [Papa Don't Take No Mess, samplingUsage, widely sampled in hip hop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: samplingUsage Context triple: [Papa Don't Take No Mess, samplingUsage, widely sampled in hip hop]
-
A.
spaceUsage
Indicates how much physical or storage space is occupied or utilized by an entity relative to the total available space.
-
B.
gridUsage
Indicates how much and in what way an entity consumes or relies on a shared grid-based resource, such as an electrical or data grid.
-
C.
usesSamplingOf
chosen
Indicates that one entity employs or relies on a sample or subset derived from another entity for its operation, analysis, or processing.
-
D.
trackUsage
Indicates that one entity monitors and records how another entity or resource is being used over time.
-
E.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf6e29881908ddb8efca9a456a3 |
completed | April 14, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69dbc873052c8190b33ff7f7c5a4e7ee |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:17 p.m.