Triple
T36634309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Even Break (Never Give a Sucker) |
E904411
|
entity |
| Predicate | hasPercussionFocus |
P158489
|
FINISHED |
| Object | drums |
—
|
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: drums | Statement: [An Even Break (Never Give a Sucker), hasPercussionFocus, drums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPercussionFocus Context triple: [An Even Break (Never Give a Sucker), hasPercussionFocus, drums]
-
A.
hasPrimaryInstrumentFocus
Indicates that an entity’s main emphasis or specialization is centered on a particular instrument.
-
B.
hasPowerfulPercussion
Indicates that an entity features or produces percussion that is notably strong, intense, or forceful in impact.
-
C.
percussionFocus
chosen
Indicates a focus on playing, studying, or emphasizing percussion instruments or percussion-related activity within a musical context.
-
D.
hasEnsembleFocus
Indicates that something is primarily concerned with, centered on, or designed for an ensemble rather than individual elements.
-
E.
percussionType
Indicates the specific kind or category of percussion instrument associated with an entity.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.