Triple
T24234458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sap (EP) |
E601834
|
entity |
| Predicate | mainInstrumentOnRecording |
P103937
|
FINISHED |
| Object | bass guitar |
—
|
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: bass guitar | Statement: [Sap (EP), mainInstrumentOnRecording, bass guitar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainInstrumentOnRecording Context triple: [Sap (EP), mainInstrumentOnRecording, bass guitar]
-
A.
coreInstrument
Indicates that an instrument plays a central or primary role in performing an action or achieving an outcome.
-
B.
mainInstrumentalProducer
Indicates that one entity serves as the primary producer responsible for the instrumental (non-vocal) component of another entity, such as a song or recording.
-
C.
bassPlayerOnRecording
chosen
Indicates that an entity serves as the bass player performing on a particular recording.
-
D.
parentInstrument
Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
-
E.
hostInstrument
Indicates that one entity serves as the instrument or platform that hosts, carries, or enables another entity or process.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28a9a4b708190851504c302778fd2 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:02 a.m.