Triple
T38420732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bigsby vibrato |
E903218
|
entity |
| Predicate | oftenFactoryInstalledOn |
P196930
|
FINISHED |
| Object | Gretsch hollow-body 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: Gretsch hollow-body guitars | Statement: [Bigsby vibrato, oftenFactoryInstalledOn, Gretsch hollow-body guitars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenFactoryInstalledOn Context triple: [Bigsby vibrato, oftenFactoryInstalledOn, Gretsch hollow-body guitars]
-
A.
neverActuallyInstalled
Indicates that an entity was planned or referenced for installation but was ultimately never installed or put into effect.
-
B.
preinstalledOn
Indicates that a software or component comes already installed and ready to use on a particular device or system before the user receives it.
-
C.
installedFor
Indicates that something has been set up or put in place to be used by or on behalf of a particular entity.
-
D.
oftenConfiguredAs
Indicates that one entity is frequently set up, arranged, or used in the form or role of another entity.
-
E.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
- F. None of above. chosen
Provenance (4 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_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
| PDg | Predicate description generation | batch_69fe6e4801108190a6be6bec2d52a1b9 |
completed | May 8, 2026, 11:14 p.m. |
Created at: May 3, 2026, 4:31 p.m.