Triple
T38420734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bigsby vibrato |
E903218
|
entity |
| Predicate | oftenAftermarketInstalledOn |
P190786
|
FINISHED |
| Object | Les Paul-style guitars |
—
|
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: Les Paul-style guitars | Statement: [Bigsby vibrato, oftenAftermarketInstalledOn, Les Paul-style guitars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenAftermarketInstalledOn Context triple: [Bigsby vibrato, oftenAftermarketInstalledOn, Les Paul-style guitars]
-
A.
aftermarketSupport
Indicates that one entity provides maintenance, service, or assistance for another entity after the initial sale or deployment.
-
B.
oftenFactoryInstalledOn
Indicates that an item is commonly pre-installed by the manufacturer on another item before it is delivered to the end user.
-
C.
aftermarketAccessories
chosen
Indicates that one entity provides or is associated with accessories added to a product after its original manufacture or sale.
-
D.
installedAfter
Indicates that one installation event occurred later in time than another installation event.
-
E.
hasAfterburnerOption
Indicates that an entity offers or is equipped with an optional afterburner capability.
- 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:31 p.m.