Triple
T20866213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Headhunters |
E513768
|
entity |
| Predicate | notableInstrumentFocus |
P9123
|
FINISHED |
| Object | electric bass |
—
|
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: electric bass | Statement: [The Headhunters, notableInstrumentFocus, electric bass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInstrumentFocus Context triple: [The Headhunters, notableInstrumentFocus, electric bass]
-
A.
notableInstrument
chosen
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
B.
notableInstrumentFeature
Indicates that an instrument is distinguished by a particular characteristic, quality, or component that is especially noteworthy or defining.
-
C.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
-
D.
notableInstrumentTechnique
Indicates that an entity is particularly recognized for using, developing, or being associated with a specific musical instrument technique.
-
E.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c460807c8190a337d8cc6c7b1438 |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.