Triple
T37053718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernie Ball Music Man James Valentine signature guitar |
E917115
|
entity |
| Predicate | neckPickup |
P65513
|
FINISHED |
| Object | Music Man custom wound humbucker |
—
|
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: Music Man custom wound humbucker | Statement: [Ernie Ball Music Man James Valentine signature guitar, neckPickup, Music Man custom wound humbucker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neckPickup Context triple: [Ernie Ball Music Man James Valentine signature guitar, neckPickup, Music Man custom wound humbucker]
-
A.
neckPickupType
chosen
Indicates the type or configuration of the pickup installed at the neck position of an instrument.
-
B.
hasPickguard
Indicates that an instrument or object is equipped with or features a pickguard.
-
C.
neckCharacteristic
Indicates that an entity has a specific attribute, feature, or quality related to its neck.
-
D.
rackPosition
Indicates the spatial placement or slot of an item within a rack or racking system.
-
E.
stickPlacement
Indicates the spatial arrangement or positioning of a stick relative to other objects or a reference frame.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.