Triple
T30466914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Jake Clemons Band |
E775166
|
entity |
| Predicate | hasLeadInstrumentalist |
P124223
|
FINISHED |
| Object | Jake Clemons |
—
|
NE NERFINISHED |
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: Jake Clemons | Statement: [The Jake Clemons Band, hasLeadInstrumentalist, Jake Clemons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadInstrumentalist Context triple: [The Jake Clemons Band, hasLeadInstrumentalist, Jake Clemons]
-
A.
hasPrimaryMusician
Indicates that an entity has a specific musician designated as its main or principal performer.
-
B.
hasKeyInstrumentalist
chosen
Indicates that an entity (such as a musical work or performance) has a primary or featured instrumental performer associated with it.
-
C.
associatedInstrumentalist
Indicates that an instrumentalist is connected to or involved with another entity, such as a work, performance, or recording, in a relevant musical role.
-
D.
hasGuitarist
Indicates that an entity has, employs, or is associated with a guitarist as part of it.
-
E.
typicalLeadInstrument
Indicates that an instrument is commonly used as the primary or lead instrument in a given musical context or performance.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 29, 2026, 8:11 p.m.