Triple
T35567835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Do My Thang |
E1027825
|
entity |
| Predicate | featuresInstrumentalPerformanceBy |
P121452
|
FINISHED |
| Object | Dâm-Funk |
E1027819
|
NE 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: Dâm-Funk | Statement: [Do My Thang, featuresInstrumentalPerformanceBy, Dâm-Funk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresInstrumentalPerformanceBy Context triple: [Do My Thang, featuresInstrumentalPerformanceBy, Dâm-Funk]
-
A.
hasInstrumentalPerformer
chosen
Indicates that an action, event, or work is performed or carried out by an entity serving as its instrumental performer.
-
B.
instrumentalBy
Indicates that an action or outcome is achieved, carried out, or mediated through the use of a particular instrument, means, or tool.
-
C.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
D.
performsMusicFrom
Indicates that one entity presents or executes a musical work that originates from or was created by another entity.
-
E.
featuresSoloPerformancesBy
Indicates that the subject includes or showcases solo performances carried out by the specified performer or performers.
- F. None of above.
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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfae8d3c819087b14c2e1c81f472 |
completed | June 23, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.