Triple
T25190475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Sensation |
E630855
|
entity |
| Predicate | sampledInBy |
P67244
|
FINISHED |
| Object | Marky Mark and the Funky Bunch |
—
|
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: Marky Mark and the Funky Bunch | Statement: [Love Sensation, sampledInBy, Marky Mark and the Funky Bunch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampledInBy Context triple: [Love Sensation, sampledInBy, Marky Mark and the Funky Bunch]
-
A.
hasBeenSampledIn
Indicates that an entity has been selected or taken as a sample within a specified context, location, or dataset.
-
B.
workSampledBy
chosen
Indicates that a work (such as a song or recording) incorporates a portion of another work through sampling.
-
C.
usesSamplingOf
Indicates that one entity employs or relies on a sample or subset derived from another entity for its operation, analysis, or processing.
-
D.
surveyedIn
Indicates that an entity was included as part of the scope or coverage of a particular survey or data-collection effort.
-
E.
basedOnSampleOf
Indicates that something is derived, inferred, or constructed from a particular sample or subset of data rather than from the entire population.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e0dc9908190b2d957d9c6314cfc |
completed | May 1, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:45 p.m.