Triple
T3776563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Real Friends |
E83320
|
entity |
| Predicate | primaryInstrumentalStyle |
P50863
|
FINISHED |
| Object | sparse drum programming |
—
|
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: sparse drum programming | Statement: [Real Friends, primaryInstrumentalStyle, sparse drum programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryInstrumentalStyle Context triple: [Real Friends, primaryInstrumentalStyle, sparse drum programming]
-
A.
primaryInstrumentAbbreviation
Indicates that one entity is the standard shortened or abbreviated form of the name of another entity’s primary instrument.
-
B.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
C.
secondaryInstrument
Indicates that an entity uses or is associated with a second, supporting instrument in addition to a primary one.
-
D.
typeOfInstrument
Indicates the specific kind or category of instrument associated with an entity.
-
E.
instrumentalIn
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc5be3c48190a72e840d8214bb74 |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc0fe3e3c8190bd886c7745c172a0 |
completed | March 8, 2026, 6:33 p.m. |
Created at: March 8, 2026, 3:36 p.m.