Triple
T16715714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings of Rhythm |
E406218
|
entity |
| Predicate | primaryInstrumentalRole |
P30063
|
FINISHED |
| Object | backing band |
—
|
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: backing band | Statement: [Kings of Rhythm, primaryInstrumentalRole, backing band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryInstrumentalRole Context triple: [Kings of Rhythm, primaryInstrumentalRole, backing band]
-
A.
primaryInstrumentalFocus
Indicates that one entity serves as the main or most emphasized instrument or means by which another entity performs an action or achieves an effect.
-
B.
primaryActor
chosen
Indicates that the referenced entity is the main participant or most central party responsible for the action or event in the relationship.
-
C.
primaryInstrumentAbbreviation
Indicates that one entity is the standard shortened or abbreviated form of the name of another entity’s primary instrument.
-
D.
primaryPosition
Indicates the main role, job, or position an entity holds among potentially multiple positions.
-
E.
primaryInstrumentalForces
Indicates that the subject represents the main or dominant forces used to produce, drive, or effect the object.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38655b54c81908c2cf7b42df996a4 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.