Triple
T10572203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fisticuffs |
E249509
|
entity |
| Predicate | primaryRoleInMusic |
P24740
|
FINISHED |
| Object | production |
—
|
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: production | Statement: [Fisticuffs, primaryRoleInMusic, production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleInMusic Context triple: [Fisticuffs, primaryRoleInMusic, production]
-
A.
featuresPrimaryInstrument
Indicates that an entity is associated with the main or most prominent instrument used or highlighted in another entity (such as a work, performance, or recording).
-
B.
primaryInstrumentalStyle
Indicates the main instrumental style or genre most closely associated with an entity’s musical performance or work.
-
C.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
D.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
E.
primaryVocalist
Indicates that the subject is the main singer or lead vocal performer for the object (such as a song, track, or musical work).
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52747a8d88190ab59333937180edc |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:37 p.m.